From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: Sven Joachim <svenjoac@gmx.de>, <ding@gnus.org>, bugs@gnus.org
Subject: Re: gnus-article-hide-headers beeps: Buffer is read-only
Date: Mon, 06 Aug 2007 10:46:55 +0900 [thread overview]
Message-ID: <b4my7gptoxc.fsf@jpl.org> (raw)
In-Reply-To: <v9wswb6nuw.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib wrote:
> Katsumi, the problem was introduced by this change ...
[...]
> I think the wrong value of inhibit-read-only was just a mistake
> (replacing "buffer-read-only" with "inhibit-read-only"?).
Oops. I must have been half asleep.
> But the ChangeLog doesn't say anything about removing (save-excursion
> (save-restriction ...)).
Not `removing' but I did `moving' them to the places just in
front of what need to perform them (for two `set-buffer's, and
for `article-narrow-to-head'). That change makes no difference
in the actual behavior but I might have thought it clarifies the
meaning of the source code.
> I doubt the other occurrence of "(inhibit-read-only nil)" in
> `gnus-x-splash' is correct. Is it?
> --8<---------------cut here---------------start------------->8---
> revision 7.17
> date: 2007/06/07 11:59:35; author: yamaoka; state: Exp; lines: +79 -34
> * gnus-ems.el (gnus-x-splash): Make it work.
> --8<---------------cut here---------------end--------------->8---
That must be a mistake, too. I've fixed it in the v5-10 branch
(it will be merged into Emacs and the Gnus trunk together with
your fix). Thank you very much for investigating these.
Regards,
prev parent reply other threads:[~2007-08-06 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87d4y3mf3z.fsf@gmx.de>
2007-08-04 20:33 ` Reiner Steib
2007-08-04 21:17 ` Sven Joachim
2007-08-06 1:46 ` Katsumi Yamaoka [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=b4my7gptoxc.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=Reiner.Steib@gmx.de \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
--cc=svenjoac@gmx.de \
/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).