From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Read-only message separator
Date: Fri, 04 Feb 2011 13:47:09 -0800 [thread overview]
Message-ID: <87vd0zo4ki.fsf@gnus.org> (raw)
In-Reply-To: <87zkqbo51p.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> in XEmacs, it works as you'd expect. It inserts a read-only string. So
> I don't seem to be able to reproduce this bug.
Actually, when using XEmacs on this function, it breaks badly, and I
have no idea why. I've reverted the change for the moment, but we
should investigate why it fails and reinstate the read-onlyness.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-02-04 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 19:41 Michael Piotrowski
2011-02-04 21:31 ` Lars Ingebrigtsen
2011-02-04 21:36 ` Lars Ingebrigtsen
2011-02-04 21:47 ` Lars Ingebrigtsen [this message]
2011-02-05 9:42 ` Michael Piotrowski
2011-02-07 18:19 ` Ted Zlatanov
2011-02-14 3:20 ` Lars Ingebrigtsen
2011-02-14 15:04 ` Ted Zlatanov
2011-02-20 17:14 ` Julien Danjou
2011-02-21 23:20 ` 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=87vd0zo4ki.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).