From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/64646 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: Exiting groups moves the cursor to next line Date: Tue, 15 May 2007 11:13:48 +0900 Organization: Emacsen advocacy group Message-ID: References: <87tzun798w.fsf@lrde.org> <878xbz6m9b.fsf@lrde.org> <87r6pog8qx.fsf@lrde.org> <87bqgqm5wd.fsf@lrde.org> <873b1z5u6x.fsf@lrde.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1179195307 29605 80.91.229.12 (15 May 2007 02:15:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 15 May 2007 02:15:07 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M13157@lists.math.uh.edu Tue May 15 04:15:05 2007 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1HnmZ3-00044R-CV for ding-account@gmane.org; Tue, 15 May 2007 04:15:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1HnmY5-0004td-Eb; Mon, 14 May 2007 21:14:01 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1HnmY2-0004tH-Ek for ding@lists.math.uh.edu; Mon, 14 May 2007 21:13:58 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.67) (envelope-from ) id 1HnmXz-0004N5-UQ for ding@lists.math.uh.edu; Mon, 14 May 2007 21:13:58 -0500 Original-Received: from orlando.hostforweb.net ([216.246.45.90]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1HnmXy-0004jJ-00 for ; Tue, 15 May 2007 04:13:55 +0200 Original-Received: from [66.225.201.151] (port=33595 helo=mail.jpl.org) by orlando.hostforweb.net with esmtpa (Exim 4.63) (envelope-from ) id 1HnmXw-0003VX-PL for ding@gnus.org; Mon, 14 May 2007 21:13:53 -0500 Mail-Copies-To: never X-Hashcash: 1:20:070515:ding@gnus.org::PE7Ub3LrHnjH8CsC:00000lRw X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (gnu/linux) Cancel-Lock: sha1:2at8vN7ZyXMqRmzdrGtBbUZqesk= X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.4 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:64646 Archived-At: >>>>> In <873b1z5u6x.fsf@lrde.org> Micha=EBl Cadilhac wrote: > Katsumi Yamaoka writes: >> 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=A0:-) Well, it's not completely the > same thing, isn't it? Yes, they are not the same. While `gnus-group-goto-unread' decides where the point is moved to, `gnus-summary-next-group-on-exit' decides whether to move the point or not and is preferred than the former if it is nil. `g-g-g-u' is used also for cases other than simply exiting the summary buffer; the most typical one is the `n' command in the group buffer, although it is named `unread' and there is even the `N' command[1]. I'd been using `g-g-g-u' with the nil value, but I can replace it with setting `g-s-n-g-o-e' to nil if it is effective also when I use the `Q' command in the summary buffer. Why I needed to set `g-g-g-u' to nil is that I have all my mail groups always visible (even if there is no unread article) in the group buffer. In the case where there are many mail groups having no unread articles, I don't want Gnus to move the point far far away. >> 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? :-) I think it is not a matter how long you've been improving Gnus. :-) > There's also two other occurrences of (gnus-group-next-unread-group 1), > but it's not really a =AB summary exit =BB 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) > [...]) IMHO, `gnus-summary-next-group-on-exit' should be effective also for them, in the viewpoint that some of those who set it to nil have a lot of visible groups having no unread article. ;-) [1] I think it is better to make `gnus-group-next-unread-group' behave as its name, regardless of the value of `gnus-group-goto-unread'. So does `gnus-group-prev-unread-group'. Because there seems to be no means to move the point to an unread group automatically for users who set `gnus-group-goto-unread' to nil, `gnus-group-catchup-current' works on even groups in which there is no unread article when two or more groups are marked if `gnus-group-goto-unread' is nil... Regards, P.S. Please ignore it but I hit on a plan; setting `gnus-group-goto-unread' to `never' might become a substitute of setting `gnus-summary-next-group-on-exit' to nil.