From: Michael Cook <cook@sightpath.com>
Subject: Re: forward-paragraph
Date: 28 Jul 1999 14:00:41 -0400 [thread overview]
Message-ID: <80k8rklkmu.fsf@lucy.sightpath.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "03 Jul 1999 11:55:17 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> > More data... When this odd behavior starts happening, if I exit
> > from gnus (don't need to exit from emacs), and restart gnus, the
> > problem goes away. I'm running GNU Emacs 20.3.1.
>
> The only thing that sets the variable in question is message.el, and
> it makes it buffer-local first. Do you have any hooks that set it or
> something?
It turns out that `fill-prefix' is causing forward-paragraph to
misbehave. In the *Article* buffer, `fill-prefix' has acquired a
buffer-local value of " " (i.e., several spaces).
By quitting and restarting gnus, I apparently force gnus to destroy
and recreate the *Article* buffer, thereby discarding the
buffer-local value.
Looking in w3-display.el, I see this code:
(defsubst w3-set-fill-prefix-length (len)
(setq fill-prefix (if (< len (- (or w3-strict-width (window-width)) 4))
(w3-get-pad-string len)
(url-warn
'html
"Runaway indentation! Too deep for window width!")
fill-prefix)))
This would be consistent with the pattern I think I've been seeing:
that forward-paragraph ceases to work right in all articles after
viewing any HTML article.
I've noticed in other situations that setting buffer-local variables
in the *Article* buffer has a kind of lingering effect.
So, here's a question: When gnus starts "rendering" an article into
an *Article* buffer, shouldn't gnus first kill-all-local-variables?
Perhaps this:
--- gnus-art.el.~1~ Fri Jul 9 18:22:56 1999
+++ gnus-art.el Wed Jul 28 13:57:20 1999
@@ -2520,6 +2520,7 @@
(current-buffer))
(save-excursion
(set-buffer (gnus-get-buffer-create name))
+ (kill-all-local-variables)
(gnus-article-mode)
(make-local-variable 'gnus-summary-buffer)
(gnus-summary-set-local-parameters gnus-newsgroup-name)
M.
next prev parent reply other threads:[~1999-07-28 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-16 16:13 forward-paragraph Michael Cook
1999-06-24 15:15 ` forward-paragraph Michael Cook
1999-07-03 9:55 ` forward-paragraph Lars Magne Ingebrigtsen
1999-07-28 18:00 ` Michael Cook [this message]
1999-07-30 15:15 ` forward-paragraph Michael Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80k8rklkmu.fsf@lucy.sightpath.com \
--to=cook@sightpath.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).