From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/83110 Path: news.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: How to alter behavior of 'gnus-summary-next-article' Date: Sat, 04 May 2013 12:05:11 -0400 Organization: Still searching... Message-ID: <8761yyhgso.fsf@newsguy.com> References: <87ip2za5yb.fsf@newsguy.com> <87haijii0u.fsf@ericabrahamsen.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1367683591 3689 80.91.229.3 (4 May 2013 16:06:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 May 2013 16:06:31 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M31376@lists.math.uh.edu Sat May 04 18:06:30 2013 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UYeyj-0004tY-3K for ding-account@gmane.org; Sat, 04 May 2013 18:06:29 +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 1UYexx-0004Kq-TS; Sat, 04 May 2013 11:05:41 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1UYexw-0004Kf-9G for ding@lists.math.uh.edu; Sat, 04 May 2013 11:05:40 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1UYexv-0006LX-2Y for ding@lists.math.uh.edu; Sat, 04 May 2013 11:05:40 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1UYext-0000Kc-Nk for ding@gnus.org; Sat, 04 May 2013 18:05:37 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UYexs-000452-Tz for ding@gnus.org; Sat, 04 May 2013 18:05:36 +0200 Original-Received: from z65-50-57-227.ips.direcpath.com ([65.50.57.227]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 May 2013 18:05:36 +0200 Original-Received: from reader by z65-50-57-227.ips.direcpath.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 May 2013 18:05:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: z65-50-57-227.ips.direcpath.com User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.0.92 (gnu/linux) Cancel-Lock: sha1:/AvVAAqC90OpS6hMXvquYl/39qQ= X-Spam-Score: -4.4 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:83110 Archived-At: Eric Abrahamsen writes: > Harry Putnam writes: > >> When opening a group and using gnus-summary-next-article ('N') to find >> first unread gnus finds the message but then opens it too. I'd like to >> just find the next new message but NOT open it. >> >> Is there an existing command that does that? If not how might I piece >> together something that would allow me to do that with a minimal >> key press? > > I don't think that anything like that is bound by default, but calling > (gnus-summary-find-next t) in the summary buffer should do what you > want. Also see gnus-summary-find-prev. You could wrap that in your own > defun with an interactive declaration, and bind it to a key. Thank you, and yes (gnus-summary-find-next t) does sort of work. Oddly I found this behavior on my first couple of tests: In a summary buffer (this group) with just 3 unread; first eval of (gnus-summary-find-next t) goes to next unread and does not open it. Whoopee, just what I was after Next eval goes to next unread as expected. But now the next unread is in a thread under the article found by the previous (above) eval. (Second eval of (gnus-summary-find-next t)) So when I eval (gnus-summary-find-next t) for the third time, instead of finding the next unread message which is in a thread... the cursor runs to the far right of the summary subject line found by previous eval. (eval number 2) That is, it doesn't open the thread but runs to the end of summary line of the unread message in the thread above it which is the top of thread. I vaguely remember something about this coming up a good while ago where gnus cursor behaves as above but don't recall what if any solution there was. PS - when OP first posted.. I was running a few mnth old version of ma gnus but as of this message now running latest ma gnus. So my tests and report above were done on latest ma gnus. Ma Gnus v0.8