From: Fabrice Gamberini <fabrice.gamberini@wavecom.fr>
Cc: Fabrice Gamberini <fabrice.gamberini@wavecom.fr>, ding@gnus.org
Subject: Re: Supercite/Message woes
Date: 06 Oct 2000 12:58:30 +0200 [thread overview]
Message-ID: <wk66n6jkx5.fsf@wmp-pc40.wavecom.fr> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "06 Oct 2000 12:31:07 +0200"
>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
FGA>> problem description --snipped--
Kai> Hm. Hmmm... That's quite strange. I just did the following test: I
Kai> typed "xxx" at the beginning of a line, then hit `C-x .'. This set
Kai> the fill-prefix to "xxx". Then I deleted the line and started typing
Kai> on a fresh line. And sure enough, when I reached the end of the line
Kai> and auto-fill kicked in, the second line began with "xxx".
Did you try that with sc-auto-fill-region-p on ?? (I think it's C-c C-p C-t f)
Here the wrong-fill-prefix-problem seems to have disappeared after setting
sc-auto-fill-region-p to nil. This comes from re-reading the SuperCite
manual and experimenting with the stuff I didn't understand at first. Not that
I can claim to have a clear understanding of everything now, but at least it
works. Plus it doesn't auto-cite on text _between_ cited paragraphs, which I
think is a wrond thing to do, so it's actually better than what you describe,
I don't have to backspace on bl**dy indented paragraphs anymore. Me Happy.
Kai> When you turn on adaptive fill and fill-prefix is nil, then Emacs
Kai> tries to figure out a fill prefix to use from the current buffer
Kai> contents. In particular, it looks at the beginning of the current
Kai> paragraph for a fill prefix to use. (Normally at the second line,
Kai> but for single-line paragraphs, it also looks at the first line.)
Kai> You can type `ESC {' and `ESC }' to go backward/forward a paragraph.
Kai> This also tells you where Emacs thinks a paragraph starts.
Kai> For me, blank lines delimit paragraphs, so when I type just below a SC
Kai> 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.
Kai> 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.
Kai> See?
Yes, this doesn't seem quite right to me though, it gets confusing to read,
isn't it ?
The more I understand, the more I think this "feature" is A Bad
Thing. (sc-auto-fill, I mean)
Kai> Maybe this is what happens to you?
Well, It might be something like this, but this happened in 2 _different_
messages, which was a source of extreme confusion and bafflement. All it took
was a single -documented though quite badly IMHO- variable to solve this
misbehaviour.
Kai> kai
Kai> --
Kai> I like BOTH kinds of music.
Thanks for looking this in.
Fabrice
--
Fabrice Gambérini
-- = Wavecom S.A. = --
Email: fabrice.gamberini@wavecom.fr
next prev parent reply other threads:[~2000-10-06 10:58 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
2000-10-06 10:58 ` Fabrice Gamberini [this message]
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=wk66n6jkx5.fsf@wmp-pc40.wavecom.fr \
--to=fabrice.gamberini@wavecom.fr \
--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).