From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: Scrolling the article at point in gnus-summary-mode
Date: Thu, 29 Nov 2007 10:17:06 +0100 [thread overview]
Message-ID: <87tzn5l8bx.fsf@member.fsf.org> (raw)
In-Reply-To: <87odddsawt.fsf@escher.local.home> (Stephen Berman's message of "Thu, 29 Nov 2007 09:39:30 +0100")
Stephen Berman <Stephen.Berman@gmx.net> writes:
>> But if the article in *article* is _not_ the article the point is on
>> in the summary buffer, then RET will scroll the wrong article. RET
>> should make sure that the article at point in the summary buffer and
>> article in *article* are the same before scrolling.
>>
>> Did someone else already encounter this issue?
>
> I think I've seen this.
Me, too.
> I have definitely observed the following, which I suppose is related:
> When more than one Gnus Summary buffer is open, typing h in the
> Article buffer goes to that last selected Summary buffer, even if the
> article comes from another Summary buffer. I suppose this has to do
> with Gnus only having one *Article* buffer, while allowing multiple
> Summary buffers, which are differently named.
You can have one article buffer per summary buffer.
,----[ C-h v gnus-single-article-buffer RET ]
| gnus-single-article-buffer is a variable defined in `gnus-sum.el'.
| Its value is t
|
| Documentation:
| *If non-nil, display all articles in the same buffer.
| If nil, each group will get its own article buffer.
|
| You can customize this variable.
`----
Or to have several article buffers in the same summary buffer, have a
look at:
,----[ (info "(gnus)Sticky Articles") ]
| When you select an article the current article buffer will be reused
| according to the value of the variable `gnus-single-article-buffer'.
| If its value is non-`nil' (the default) all articles reuse the same
| article buffer. Else each group has its own article buffer.
|
| This implies that it's not possible to have more than one article
| buffer in a group at a time. But sometimes you might want to display
| all the latest emails from your mother, your father, your aunt, your
| uncle and your 17 cousins to coordinate the next christmas party.
|
| That's where sticky articles come in handy. A sticky article buffer
| basically is a normal article buffer, but it won't be reused when you
| select another article.
`----
Nevertheless, your and Bastien's problems look like a bug.
Bye,
Tassilo
next prev parent reply other threads:[~2007-11-29 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 17:01 Bastien
2007-11-29 8:39 ` Stephen Berman
2007-11-29 9:17 ` Tassilo Horn [this message]
2007-11-29 22:37 ` Stephen Berman
2007-11-30 1:45 ` Bastien
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=87tzn5l8bx.fsf@member.fsf.org \
--to=tassilo@member.fsf.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).