From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: =1= message: insert mail-header-separator read-only and intangible
Date: Fri, 04 Feb 2011 00:47:53 -0800 [thread overview]
Message-ID: <87mxmckwxy.fsf@gnus.org> (raw)
In-Reply-To: <b4mipx0wt8c.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> + (let ((message-forbidden-properties nil))
>> + (insert (propertize (concat mail-header-separator "\n")
>> + 'read-only t 'rear-nonsticky t 'intangible t)))
>
> Why does it need to let-bind?
Yes, that seems odd. Binding that const there won't have any effect,
will it?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-02-04 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Pl14t-0002by-00@quimby.gnus.org>
2011-02-04 0:14 ` Katsumi Yamaoka
2011-02-04 8:47 ` Lars Ingebrigtsen [this message]
2011-02-04 10:14 ` Julien Danjou
2011-02-04 10:15 ` Lars Ingebrigtsen
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=87mxmckwxy.fsf@gnus.org \
--to=larsi@gnus.org \
--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).