From: bojohan+news@dd.chalmers.se (Johan Bockgård)
To: ding@gnus.org
Subject: Re: Exiting groups moves the cursor to next line
Date: Sat, 30 Jun 2007 14:03:45 +0200 [thread overview]
Message-ID: <yoijhcopy7ha.fsf@remote5.student.chalmers.se> (raw)
In-Reply-To: <87bqgo1flr.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> "Old" means anything unsubscribed (I keep bits of occasional interest
> in unsubscribed level), or anything with no unread articles (which is
> not necessarily old, but is certainly a case of going back to
> revisit).
My preference is
;; Kludge ahead
(defadvice gnus-group-next-unread-group (around summary-exit activate)
(if (boundp 'group-point)
(let ((gnus-level-subscribed (max gnus-level-subscribed
(gnus-group-group-level))))
ad-do-it)
ad-do-it))
to make the call to `gnus-group-next-unread-group' inside
`gnus-summary-exit' not insist on selecting a subscribed group, but
to instead advance to the next unread group on the same level or
better. I might have a whole bundle of seldomly read groups and i don't
want point to jump far away.
A more friendly way to do this would be welcome.
--
Johan Bockgård
prev parent reply other threads:[~2007-06-30 12:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 11:21 exiting digest mails does not move " Shanks N
2007-05-06 14:00 ` Katsumi Yamaoka
2007-05-08 12:18 ` Katsumi Yamaoka
2007-05-08 14:25 ` Shanks N
2007-05-09 8:25 ` Katsumi Yamaoka
2007-05-08 13:09 ` Exiting groups moves the cursor to next line (was: exiting digest mails does not move the cursor to next line) Michaël Cadilhac
2007-05-08 17:44 ` Exiting groups moves the cursor to next line Reiner Steib
2007-05-08 21:25 ` Michaël Cadilhac
2007-05-10 12:31 ` Michaël Cadilhac
2007-05-12 15:13 ` Michaël Cadilhac
2007-05-13 23:01 ` Katsumi Yamaoka
2007-05-14 14:57 ` Michaël Cadilhac
2007-05-15 2:13 ` Katsumi Yamaoka
2007-05-18 1:33 ` Kevin Ryde
2007-05-18 1:56 ` Katsumi Yamaoka
2007-05-13 23:14 ` Kevin Ryde
2007-05-14 15:13 ` Michaël Cadilhac
2007-06-30 12:03 ` Johan Bockgård [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=yoijhcopy7ha.fsf@remote5.student.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
--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).