Gnus development mailing list
 help / color / mirror / Atom feed
From: michael@cadilhac.name (Michaël Cadilhac)
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: Exiting groups moves the cursor to next line
Date: Mon, 14 May 2007 16:57:42 +0200	[thread overview]
Message-ID: <873b1z5u6x.fsf@lrde.org> (raw)
In-Reply-To: <b4mhcqgqqek.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon\, 14 May 2007 08\:01\:39 +0900")

[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> In <87r6pog8qx.fsf@lrde.org> Michaël Cadilhac wrote:
>
>> + 2007-05-10  Michaël Cadilhac  <michael@cadilhac.name>
>> +
>> + 	* gnus-sum.el (gnus-summary-next-group-on-exit): New variable.  Tell if, on
>> + 	summary exit, the next group has to be selected.
>> + 	(gnus-summary-exit): Use it.
>
> Only setting `gnus-group-goto-unread' to nil has been sufficient
> for me but that's ok.;-)

I _need_ to do things the hard way :-) Well, it's not completely the
same thing, isn't it?

> Why don't you use `gnus-summary-next-group-on-exit' in
> `gnus-summary-exit-no-update' too?

Simple: because I'm a newcomer in Gnus patching, and I had to make an
error.  Was quite obvious, nop? :-)

There's also two other occurrences of (gnus-group-next-unread-group 1),
but it's not really a « summary exit » so I don't know if I should put
the test there:

In gnus-summary-read-group-1:

     ;; We couldn't select this group.
     ((null did-select)
        [...]
	(gnus-group-next-unread-group 1)
        [...])

     ;; The user did a `C-g' while prompting for number of articles,
     ;; so we exit this group.
     ((eq did-select 'quit)
        [...]
	(gnus-group-next-unread-group 1)
        [...])

-- 
 |   Michaël `Micha' Cadilhac       |   Did you Mooh today ?                 |
 |   http://michael.cadilhac.name   |                                        |
 |   JID/MSN:                       |       http://boitam.eu/                |
 `----  michael.cadilhac@gmail.com  |                                   -  --'

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2007-05-14 14:57 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 [this message]
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

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=873b1z5u6x.fsf@lrde.org \
    --to=michael@cadilhac.name \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.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).