From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: The "true" format of .mailrc
Date: 23 Aug 1999 19:12:04 +0200 [thread overview]
Message-ID: <byzozio1zv.fsf@bolzano.math.ethz.ch> (raw)
mail-abbrevs.el has this
end)
(while start
;; If we're reading from the mailrc file, then addresses are delimited
;; by spaces, and addresses with embedded spaces must be surrounded by
;; single or double-quotes. Otherwise, addresses are separated by
;; commas.
(if from-mailrc-file
(cond ((eq ?\" (aref definition start))
(setq start (1+ start)
end (string-match "\"[ \t,]*" definition start)))
((eq ?\' (aref definition start))
However my other MUA (mutt) disagrees. It always wants comments in its
alias file and generates entries like
alias joe Joe User <joe@pobox.net>
mail-abbrevs.el turns this into three aliases: Joe, User,
<joe@pobox.net>.
Unfortunately mutt also doesn't remove the quotes from
alias joe "Joe User <joe@pobox.net>"
A quick glance at other MUA's show that they _all_ want commas
Jan
next reply other threads:[~1999-08-23 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-23 17:12 Jan Vroonhof [this message]
1999-08-23 17:31 ` Tibor Simko
1999-08-24 16:23 ` Edward J. Sabol
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=byzozio1zv.fsf@bolzano.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
/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).