Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: How to alter behavior of 'gnus-summary-next-article'
Date: Sat, 04 May 2013 12:05:11 -0400	[thread overview]
Message-ID: <8761yyhgso.fsf@newsguy.com> (raw)
In-Reply-To: <87haijii0u.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Harry Putnam <reader@newsguy.com> 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




      reply	other threads:[~2013-05-04 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-04  1:29 Harry Putnam
2013-05-04  2:41 ` Eric Abrahamsen
2013-05-04 16:05   ` Harry Putnam [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=8761yyhgso.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --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).