From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: someone broke message-newline-and-reformat
Date: 10 Nov 2000 17:52:02 +0100 [thread overview]
Message-ID: <vafsnoz4vnx.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <eyem0jq2lf.fsf@video.uic.vsu.ru>
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. Can you make use of them in some
way? Maybe one of these needs to be changed so that
message-newline-and-reformat works correctly -- then the required
change is probably also useful for the other applications.
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).
Right now, regexes which are supposed to match citation prefixes are
scattered about the Gnus source code in various places -- this isn't a
healthy situation, imvho.
Thoughts?
kai
--
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing
next prev parent reply other threads:[~2000-11-10 16:52 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 [this message]
2000-11-11 18:35 ` dme
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=vafsnoz4vnx.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).