From: jidanni@jidanni.org
To: ding@gnus.org
Subject: Re: gnus-summary-kill-thread should also do gnus-summary-limit-to-unread
Date: Thu, 15 May 2008 08:46:19 +0800 [thread overview]
Message-ID: <878wycgzs4.fsf@jidanni.org> (raw)
In-Reply-To: <86prrr8tjk.fsf@lifelogs.com>
Anyway, try this experiment: go to a newsgroup full of boring articles
and type d d d d ... (gnus-summary-mark-as-read-forward) note that the
view doesn't jerk up until we've d'ed the very last article visible.
It should jerk up when we d the SECOND to last article. That way we
can tell if we are on the last article of a thread or not yet. How to
make it jerk up earlier for all such commands?
Wait, let's explore gnus-auto-center-summary.
Documentation:
*If non-nil, always center the current summary buffer.
In particular, if `vertical' do only vertical recentering. If non-nil
and non-`vertical', do both horizontal and vertical recentering.
But in Info we see
`gnus-auto-center-summary'
If non-`nil', Gnus will keep the point in the summary buffer
centered at all times. This makes things quite tidy, but if you
have a slow network connection, or simply do not like this
un-Emacsism, you can set this variable to `nil' to get the normal
Emacs scrolling action. This will also inhibit horizontal
re-centering of the summary buffer, which might make it more
inconvenient to read extremely long threads.
This variable can also be a number. In that case, center the
window at the given number of lines from the top.
Assuming the former is correct, I tried both
(setq gnus-auto-center-summary 'vertical)
(setq gnus-auto-center-summary "vertical")
but don't see any magic effect.
(setq gnus-auto-center-summary t) indeed does horizontal recentering
only apparently. Oy vey whatever.
prev parent reply other threads:[~2008-05-15 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 1:17 jidanni
2008-05-11 10:44 ` Reiner Steib
2008-05-12 14:51 ` Ted Zlatanov
2008-05-15 0:46 ` jidanni [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=878wycgzs4.fsf@jidanni.org \
--to=jidanni@jidanni.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).