From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Supercite/Message woes
Date: 06 Oct 2000 12:31:07 +0200 [thread overview]
Message-ID: <vaf4s2qb6s4.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <wk4s2rqof2.fsf@wmp-pc40.wavecom.fr>
On 05 Oct 2000, Fabrice Gamberini wrote:
> I have attempted a finer analysis of the problem, it really seems
> to be lying somewhere in-between bbdb and supercite. I tried
> breakpointing on the filladapt paragraph functions and the
> 'fill-prefix' variable *has* the right value when I compose a
> reply, but it is not used by whatever piece of code flows the
> lines of text around... I think I'll send the problem to the
> supercite mailing-list, though it seems this package hasn't been
> updated in ages, maybe they'll have a clue.
Hm. Hmmm... That's quite strange. I just did the following test: I
typed "xxx" at the beginning of a line, then hit `C-x .'. This set
the fill-prefix to "xxx". Then I deleted the line and started typing
on a fresh line. And sure enough, when I reached the end of the line
and auto-fill kicked in, the second line began with "xxx".
When you turn on adaptive fill and fill-prefix is nil, then Emacs
tries to figure out a fill prefix to use from the current buffer
contents. In particular, it looks at the beginning of the current
paragraph for a fill prefix to use. (Normally at the second line, but
for single-line paragraphs, it also looks at the first line.) You can
type `ESC {' and `ESC }' to go backward/forward a paragraph. This
also tells you where Emacs thinks a paragraph starts.
For me, blank lines delimit paragraphs, so when I type just below a SC
citation, the SC citation will be reused. Like so:
Foo> This is an SC citation line.
Foo> The SC citation must be at least two lines long.
And here is what I type just below that citation. The next line will
Foo> inherit the fill prefix from the second line of this paragraph,
Foo> and since this paragraph starts with two SC citation lines, the
Foo> auto-filled lines also have SC citation prefixes.
See?
Maybe this is what happens to you?
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~2000-10-06 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-04 8:46 Fabrice Gamberini
2000-10-04 18:47 ` Kai Großjohann
[not found] ` <wksnqbk7bf.fsf@wmp-pc40.wavecom.fr>
[not found] ` <vaflmw3bc4g.fsf@lucy.cs.uni-dortmund.de>
2000-10-05 15:48 ` Fabrice Gamberini
2000-10-06 10:31 ` Kai Großjohann [this message]
2000-10-06 10:58 ` Fabrice Gamberini
2000-10-06 13:53 ` Kai Großjohann
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=vaf4s2qb6s4.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).