From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: bug? message.el `message-setup-1' mail-header-separator
Date: Wed, 28 Apr 2004 16:05:39 +0200 [thread overview]
Message-ID: <m37jw0nqoc.fsf@defun.localdomain> (raw)
In-Reply-To: <quack.20040428T0537.87u0z446sy@v-woof.quarl.org> (Karl Chen's message of "28 Apr 2004 05:37:33 -0700")
Karl Chen <quarl@hkn.eecs.berkeley.edu> writes:
> Is the mail-header-separator text inserted by `message-setup-1'
> supposed to be read-only?
No, I don't think so. It breaks various stuff if you make it
read-only.
> It makes sense for it to be so, and the code actually sets it to NOT
> read-only, which seems useless since it would by default be
> read-only.
Yeah, that code appears to be completely redundant.
--
Jesper Harder <http://purl.org/harder/>
prev parent reply other threads:[~2004-04-28 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 12:37 bug? message.el `message-setup-1' mail-header-separator read-only Karl Chen
2004-04-28 14:05 ` Jesper Harder [this message]
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=m37jw0nqoc.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).