Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Bruno Hertz" <spammer.go.home@gmail.com>
Subject: Re: How to get new mail without leaving Summary buffer?
Date: Wed, 30 Mar 2005 11:49:44 +0200	[thread overview]
Message-ID: <m3d5thpio7.fsf@caruso.quasi.local> (raw)
In-Reply-To: <v94qetmt6p.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+from-uce@imap.cc> writes:

> On Wed, Mar 30 2005, Bruno Hertz wrote:
>
>> The group buffer is not entered resp. the summary buffer not left
>> here, afaik.
>
> Wrong.  The doc string clearly says so:

Partly, yes. See below.

> ,----[ `C-h k M-g' ]
> | M-g runs the command gnus-summary-rescan-group
> |    which is an interactive compiled Lisp function in `gnus-sum'.
> | It is bound to M-g, Z G, <menu-bar> <Gnus> <Exit> <Rescan group>.
> | (gnus-summary-rescan-group &optional all)
> | 
> | Exit the newsgroup, ask for new articles, and select the newsgroup.
> `----

One might still differentiate 'leaving the group' and 'leaving the buffer'.
The buffer isn't actually left on M-g when new mails are available, which
was the case during my tests. The summary is apparantly completely rebuilt,
though, as one would expect when a group is exited and reentered.

On the other hand, if no new articles are pending, the behavior described
by OP actually occurs, i.e. the group buffer pops up and you're asked
about how many articles you want to pull. So one really leaves the summary,
and (unfortunately) on hitting C-g at that point one is left in the group
buffer (would be better if the summary hadn't been destroyed at that point
- and maybe it isn't, didn't investigate that - and could be brought back,
so that one had a nondestructive check method).

Anyways, that's why I said 'doesn't leave the buffer'.

Regards, Bruno.


  reply	other threads:[~2005-03-30  9:49 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 [this message]
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
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=m3d5thpio7.fsf@caruso.quasi.local \
    --to=spammer.go.home@gmail.com \
    /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).