From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: =1= Revert "message: insert mail-header-separator read-only and intangible"
Date: Thu, 03 Feb 2011 07:49:04 -0800 [thread overview]
Message-ID: <87fws5azkf.fsf@gnus.org> (raw)
In-Reply-To: <E1Pl1N9-0002xV-00@quimby.gnus.org>
Julien Danjou <julien@danjou.info> writes:
> Revert "message: insert mail-header-separator read-only and intangible"
Any particular reason? Seemed like a good idea to me... only I'd do it
with overlays instead of text properties so that it'd be less "sticky"
when kill'n'yanking it.
Or perhaps just defaulting the separator to "" might be nicer. And
perhaps display the division with a non-textual display property of some
kind? The separator text has always annoyed me.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next parent reply other threads:[~2011-02-03 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Pl1N9-0002xV-00@quimby.gnus.org>
2011-02-03 15:49 ` Lars Ingebrigtsen [this message]
2011-02-03 15:54 ` Julien Danjou
2011-02-03 16:30 ` Julien Danjou
2011-02-03 18:12 ` Adam Sjøgren
2011-02-03 18:28 ` Adam Sjøgren
2011-02-04 9:27 ` 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=87fws5azkf.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).