From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: `n' and `p' in Group buffer
Date: 27 Nov 1997 19:53:26 +0100 [thread overview]
Message-ID: <kigafeq9nix.fsf@jagor.srce.hr> (raw)
In-Reply-To: Stefan Waldherr's message of "27 Nov 1997 13:27:35 -0500"
Stefan Waldherr <swa@cs.cmu.edu> writes:
> Your cursor is on `group4', your finger on the `n' because you used
> `n' to hop thru groups 2 and 3. Now, there is no next group with new
> mail in it, but there is a previous group with new mail. Of course,
> you don't want to press `p' -- cycle to the rescue! Good or evil?
Sounds like not really necessary. I find the `.' command very useful
in this case.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Oh lord won't you buy me a color TV...
next prev parent reply other threads:[~1997-11-27 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-27 18:27 Stefan Waldherr
1997-11-27 18:53 ` Hrvoje Niksic [this message]
1997-11-27 19:07 ` Lars Magne Ingebrigtsen
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=kigafeq9nix.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).