Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@IRO.UMontreal.CA>
Cc: ding@gnus.org
Subject: Re: Movement ops
Date: 08 Dec 1999 13:21:02 -0500	[thread overview]
Message-ID: <vrso1di99t.fsf@trex.IRO.UMontreal.CA> (raw)
In-Reply-To: Hrvoje Niksic's message of "07 Dec 1999 19:18:31 +0100"

Hrvoje Niksic <hniksic@iskon.hr> écrit:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> > After so many years of Gnus usage, I'm still looking for the right
> > keybindings.  I have now set gnus-summary-goto-unread to `never'
> > which I think is almost the right thing.  M-u and E and so on move
> > to the next article, which is okay.  And `n' and `p' move to the
> > next/previous article, which I like.

> I use `N' and `P' for this, so `n' and `p' are useful for going to the
> next/previous unread article.  But you're right; there seems to be no
> one perfect setting.

And we do not have enough keys :-).

I rebound `N' and `P' for going to the next or previous thread, as I see
that I sometimes want to postpone reading a particular thread, without
skipping it the long way.  I keep `n' and `p' for next or previous unread.
For next/previous article, I just use `C-n' and `C-p' followed by `SPC'.

-- 
François Pinard   http://www.iro.umontreal.ca/~pinard


  parent reply	other threads:[~1999-12-08 18:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-07 18:04 Kai Großjohann
1999-12-07 18:18 ` Hrvoje Niksic
1999-12-07 18:38   ` Kai Großjohann
1999-12-08 18:07     ` wjhardaker
2000-04-21 19:40     ` Lars Magne Ingebrigtsen
2000-04-21 21:41       ` Kai Großjohann
2000-04-22 12:10         ` Lars Magne Ingebrigtsen
2000-04-22 15:22           ` Kai Großjohann
2000-04-22 18:22             ` Lars Magne Ingebrigtsen
1999-12-08 18:21   ` François Pinard [this message]
1999-12-07 18:19 ` Jody M. Klymak
1999-12-07 18:37   ` Kai Großjohann
1999-12-07 18:47     ` Jody M. Klymak
1999-12-07 18:56       ` Kai Großjohann
1999-12-07 19:15         ` Jody M. Klymak
1999-12-07 21:25           ` Kai Großjohann
1999-12-07 20:54         ` Paul Stevenson

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=vrso1di99t.fsf@trex.IRO.UMontreal.CA \
    --to=pinard@iro.umontreal.ca \
    --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).