From: Eli Zaretskii <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: RMAIL against Texinfo
Date: 02 Feb 2004 07:59:08 +0200 [thread overview]
Message-ID: <un082auoj.fsf@elta.co.il> (raw)
In-Reply-To: <87isiq5uzg.fsf@emptyhost.emptydomain.de> (message from Kai Grossjohann on Sun, 01 Feb 2004 22:51:31 +0100)
> From: Kai Grossjohann <kai@emptydomain.de>
> Date: Sun, 01 Feb 2004 22:51:31 +0100
>
> This will still remove frumple-info and tex-info from the list of
> addresses.
So you are saying that using \` instead of \< would be better? (I
used \< because I thought about addresses like
<info-gnu-emacs@gnu.org>, with the brackets intact.)
> Also, there is experience with nnmail-fancy-split in Gnus, which
> automatically surrounds regexes with \\< and \\>. Users are supposed
> to say ".*foo.*" if they want to undo the effect of \\<...\\>. But
> after some years it turned out that this didn't always work, and now
> there is additional code in the function supporting nnmail-split-fancy
> which checks for the regex starting with ".*"... I forgot what
> exactly was the problem, though.
Well, do you see any reason that this would be relevant to the case
in point? mail-utils.el doesn't surround regular expressions with \<
and \>, it only does that with usernames, which aren't regexps.
> I'm afraid that with a similar change for rmail-dont-reply-to-names,
> you might fall into similar traps.
Like what?
> And it doesn't even cover all cases.
Sure, but it does make the current situation better, doesn't it?
next prev parent reply other threads:[~2004-02-02 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 17:16 RMAIL against Texinfo Eli Zaretskii
2004-02-01 21:51 ` Kai Grossjohann
2004-02-02 5:59 ` Eli Zaretskii [this message]
2004-02-02 7:33 ` Kai Grossjohann
2004-02-02 19:04 ` Eli Zaretskii
2004-02-03 8:34 ` Kai Grossjohann
2004-02-03 10:13 ` Eli Zaretskii
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=un082auoj.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.