From: Miles Bader <miles.bader@necel.com>
To: ding@gnus.org
Subject: Re: gnus-article-read-summary-keys: can't handle hidden summary buffer?
Date: Mon, 29 Sep 2008 21:20:38 +0900 [thread overview]
Message-ID: <buohc7zuort.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <b4m1vz3tdjz.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Could you test this patch?
That seems to fix the problem.
> Even in the case where the summary buffer is hidden, the summary
> window appears a moment (it is necessary for running a summary
> command)
I do notice some weird redisplay glitches where if something happens to
cause redisplay (e.g. a garbage-collection message), the summary buffer
will show up temporarily. Kind of annoying but...
Why is the summary window necessary for running a summary command?
Can't they just act on the summary buffer?
Thanks,
-Miles
--
`There are more things in heaven and earth, Horatio,
Than are dreamt of in your philosophy.'
next prev parent reply other threads:[~2008-09-29 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 4:29 Miles Bader
2008-09-29 11:08 ` Katsumi Yamaoka
2008-09-29 12:20 ` Miles Bader [this message]
2008-09-29 23:55 ` Katsumi Yamaoka
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=buohc7zuort.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--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).