From: "Jody M. Klymak" <jklymak@apl.washington.edu>
Cc: ding@gnus.org
Subject: Re: Movement ops
Date: 07 Dec 1999 10:19:12 -0800 [thread overview]
Message-ID: <k8mqaa1r.fsf@apl.washington.edu> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "07 Dec 1999 19:04:30 +0100"
Hi Kai,
My movement commands are stock, out of the box. N and P move to the
next/previous, n/p move to the next/previous unread and "." moves to
the first unread. This seems to have all the functionality you seek,
or have I missed something?
Cheers, Jody
>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
KG> After so many years of Gnus usage, I'm still looking for the
KG> right keybindings. I have now set gnus-summary-goto-unread to
KG> `never' which I think is almost the right thing. M-u and E
KG> and so on move to the next article, which is okay. And `n'
KG> and `p' move to the next/previous article, which I like. And
KG> I can use `.' to move to the first unread article.
KG> But how do I move to the next/previous unread article?
KG> kai -- A preposition is not a good thing to end a sentence
KG> with.
--
Jody Klymak APL/School of Oceanography,
Doctoral Candidate University of Washington
mailto:jklymak@apl.washington.edu (206)-685-9080
http://www.ocean.washington.edu/people/grads/jklymak/
next prev parent reply other threads:[~1999-12-07 18:19 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
1999-12-07 18:19 ` Jody M. Klymak [this message]
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=k8mqaa1r.fsf@apl.washington.edu \
--to=jklymak@apl.washington.edu \
--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).