From: dme@dme.org
Cc: Vladimir Volovich <vvv@vvv.vsu.ru>, ding@gnus.org
Subject: Re: someone broke message-newline-and-reformat
Date: 11 Nov 2000 18:35:02 +0000 [thread overview]
Message-ID: <87k8aabbmx.fsf@serafina-pekkala.dme.org> (raw)
In-Reply-To: <vafsnoz4vnx.fsf@lucy.cs.uni-dortmund.de>
* Kai.Grossjohann@CS.Uni-Dortmund.DE [2000-11-10 16:52:02]
| On 10 Nov 2000, Vladimir Volovich wrote:
| > (when (looking-at " *\\(\\w\\|[-._]\\)*>+[ \t]*\\|[]>»|:}+ \t]*")
|
| I'd be glad if these regexes weren't hard-coded. There are variables
| gnus-cite-prefix-regexp and gnus-supercite-regexp, as well as
| gnus-supercite-secondary-regexp.
gnus-cite-prefix-regexp is the relevant one (the others match
supercite attribution lines rather than body citation). With two
small additional changes (append space when inserting and use \w
rather than . (as per Vladimir)) this appears to work satisfactorily
for both supercite and `normal' citation prefixes.
| Another idea is that we might need to move gnus-cite-prefix-regexp and
| gnus-supercite-regexp to message-* variables since message.el is
| supposed to be usable without Gnus (but not vice versa).
I've done that and added (require 'message) to gnus-cite.el - is there
a better way to do this ? I'll post a diff after some more testing.
The documentation also changes slightly.
dme.
next prev parent reply other threads:[~2000-11-11 18:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 11:39 Vladimir Volovich
2000-11-10 12:20 ` dme
2000-11-10 12:58 ` dme
2000-11-10 15:16 ` Vladimir Volovich
2000-11-10 15:37 ` dme
2000-11-10 16:52 ` Kai Großjohann
2000-11-11 18:35 ` dme [this message]
2000-11-11 22:38 ` Kai Großjohann
2000-11-12 11:21 ` dme
2000-11-13 10:49 ` Vladimir Volovich
2000-11-13 12:17 ` dme
2000-11-13 12:23 ` Vladimir Volovich
2000-11-10 11:46 Vladimir Volovich
2000-11-17 11:42 Vladimir Volovich
2000-11-17 11:51 ` dme
2000-11-17 13:09 ` ShengHuo ZHU
2000-11-17 13:09 ` ShengHuo ZHU
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=87k8aabbmx.fsf@serafina-pekkala.dme.org \
--to=dme@dme.org \
--cc=ding@gnus.org \
--cc=vvv@vvv.vsu.ru \
/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).