From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/13994 Path: news.gmane.org!not-for-mail From: Leo Newsgroups: gmane.emacs.gnus.user Subject: Re: How to stop gnus from moving to the next group? Date: Wed, 12 May 2010 12:03:28 +0100 Organization: University of Cambridge Message-ID: References: <878w7pwlrv.fsf@gate450.dyndns.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1273662229 23065 80.91.229.12 (12 May 2010 11:03:49 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 12 May 2010 11:03:49 +0000 (UTC) To: info-gnus-english@gnu.org Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Wed May 12 13:03:48 2010 connect(): No such file or directory Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OC9j9-00052N-NW for gegu-info-gnus-english@m.gmane.org; Wed, 12 May 2010 13:03:48 +0200 Original-Received: from localhost ([127.0.0.1]:41656 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OC9j8-00041V-SO for gegu-info-gnus-english@m.gmane.org; Wed, 12 May 2010 07:03:46 -0400 Original-Received: from [140.186.70.92] (port=50394 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OC9j2-0003qa-OQ for info-gnus-english@gnu.org; Wed, 12 May 2010 07:03:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OC9j0-0005GG-UE for info-gnus-english@gnu.org; Wed, 12 May 2010 07:03:40 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:43841) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OC9j0-0005Ff-OZ for info-gnus-english@gnu.org; Wed, 12 May 2010 07:03:38 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OC9iy-0004xy-4k for info-gnus-english@gnu.org; Wed, 12 May 2010 13:03:36 +0200 Original-Received: from smaug.linux.pwf.cam.ac.uk ([193.60.95.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 May 2010 13:03:36 +0200 Original-Received: from sdl.web by smaug.linux.pwf.cam.ac.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 May 2010 13:03:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ connect(): No such file or directory Original-Lines: 37 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: smaug.linux.pwf.cam.ac.uk User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:edweVuOH0EtpbNBe0pbIxCsNOJA= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.gnus.user:13994 Archived-At: On 2010-05-12 09:45 +0100, Andreas Seltenreich wrote: > Leo writes: > >> On 2010-04-29 03:38 +0100, Leo wrote: >>> 1. go to a group (that has a next group with unread articles) >>> 2. C-u RET >>> 3. When there's prompt in the minibuffer asking how many articles, hit C-g >> >> I dig a bit into it. It is due to gnus-summary-read-group-1 having >> (gnus-group-next-unread-group 1) unconditionally. Should that respect >> gnus-group-goto-unread or a new customisation variable? > > It does respect it, AFAICT. > >> There could be a lot of empty groups between current and the next unread >> group. The movement is undesirable in this case. > > I agree. I don't think it is sensible to do anything beyond cleanup > when catching the C-g. After all, choosing a million articles at the > prompt and hitting C-g while Gnus is thrashing doesn't move point > either. I think making C-g trigger new action is already in violation of intuitive user expectation. Imagine if C-s move to the next occurrence when C-g. Fortunately this doesn't occur as often as C-s. Anyway I have fixed this locally. > I'll push a fix into No Gnus. In case anyone is attached to the old > behavior: Entering 0 instead of C-g at the prompt will still move point. As a user I find it difficult to appreciate such a subtle behaviour. I think making it simple and intuitive will help new users a lot. > Thanks, > andreas Leo