From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: RMAIL against Texinfo
Date: Tue, 03 Feb 2004 09:34:11 +0100 [thread overview]
Message-ID: <87y8rk4l4s.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 7494-Mon02Feb2004210458+0200-eliz@elta.co.il
"Eli Zaretskii" <eliz@elta.co.il> writes:
>> From: Kai Grossjohann <kai@emptydomain.de>
>> Date: Mon, 02 Feb 2004 08:33:54 +0100
>>
>> It seems that rmail-dont-reply-to-names is already anchored to the
>> beginning of an email address by the existing code?
>
> I think mail-strip-quoted-names removes <> and any other junk, so it
> sounds like prepending \` to "info-" would be better than \<. Do you
> agree?
In that case, sure. (I'm somewhat confused about what does the string
look like that's passed to rmail-dont-reply-to-names.)
>> >> 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.
>>
>> Didn't you suggest to automagically add \\<...\\> to the regexp
>> constructed from rmail-dont-reply-to-names?
>
> Not to rmail-dont-reply-to-names, ti the user's login name and email
> address. These two are literal strings, not regular expressions.
Oh, you're suggesting to change the default value of
rmail-dont-reply-to-names! Okay. That's something else entirely.
Sorry that I didn't get this before. Good idea.
(The beginning of rmail-dont-reply-to looks strange: in the code (if
(null X) (if X foo bar) baz) it seems like foo will never be executed.
X is rmail-dont-reply-to-names.)
> As to rmail-dont-reply-to-names, I don't think we should surround them
> with anything; it's the user's job to do so when she customizes this
> option.
Right. That's what I was trying to say.
Kai
next prev parent reply other threads:[~2004-02-03 8:34 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
2004-02-02 7:33 ` Kai Grossjohann
2004-02-02 19:04 ` Eli Zaretskii
2004-02-03 8:34 ` Kai Grossjohann [this message]
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=87y8rk4l4s.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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.