From: Anders Wirzenius <anders@no.email.thanks.invalid>
Subject: Re: How to get new mail without leaving Summary buffer?
Date: Wed, 30 Mar 2005 08:21:42 GMT [thread overview]
Message-ID: <ull8535nr.fsf@no.email.thanks.invalid> (raw)
In-Reply-To: <86ll85hcqi.fsf@pallotta.studby.uio.no>
steinab@ifi.uio.no (Steinar Børmer) writes:
> napofrog wrote:
>
> | While in a summary buffer, I'm trying to get new mail into it without
> | exiting the summary buffer. I was under the impression that this is
> | what '/ N' is for. But whether or not I have gotten new mail from the
> | server with 'g' in the Group buffer, the only thing that '/ N' ever
> | does for me is to remove everything from the current summary buffer
> | except for the message that the cursor is currently on. What should I
> | be doing instead?
>
> Actually, I think you might be doing `/ n' instead of `/ N'. That gives
> your described behavior.
>
> --
> SB
That is exactly what I am doing, too, namely `/ n'.
If I hit "c-x / N" I get:
<help buffer>
/ n runs the command gnus-summary-limit-to-articles
which is an interactive compiled Lisp function in `gnus-sum'.
(gnus-summary-limit-to-articles N)
Limit the summary buffer to the next N articles.
If not given a prefix, use the process marked articles instead.
</help buffer>
Gnus v5.9.0
GNU Emacs 21.2.1 (i386-msvc-nt5.1.2600) of 2002-03-19 on buffy
Windows XP, Cygwin
Anders
next prev parent reply other threads:[~2005-03-30 8:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 18:53 napofrog
2005-03-29 19:22 ` Bruno Hertz
2005-03-29 22:05 ` napofrog
2005-03-29 22:38 ` Bruno Hertz
2005-03-29 23:13 ` napofrog
2005-03-29 23:28 ` Bruno Hertz
2005-03-30 8:30 ` Reiner Steib
2005-03-30 9:49 ` Bruno Hertz
2005-03-29 23:18 ` Bruno Hertz
2005-03-30 6:23 ` Steinar Børmer
2005-03-30 7:31 ` Bruno Hertz
2005-03-30 6:25 ` Steinar Børmer
2005-03-30 8:21 ` Anders Wirzenius [this message]
2005-03-30 8:33 ` Reiner Steib
2005-03-30 16:29 ` napofrog
2005-03-30 20:19 ` Reiner Steib
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=ull8535nr.fsf@no.email.thanks.invalid \
--to=anders@no.email.thanks.invalid \
/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).