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 01:28:26 +0200	[thread overview]
Message-ID: <m3r7hyxc9x.fsf@caruso.quasi.local> (raw)
In-Reply-To: <1112138010.614611.24600@f14g2000cwb.googlegroups.com>

"napofrog" <napofrog@hotmail.com> writes:

> Really?  M-g very clearly exits the summary buffer for me.  Here is
> exactly what happens when I use it from the summary buffer:
>
> 1) The mini-buffer at the bottom of the frame says "Expiring
> articles..."
>
> 2) The summary buffer disappears and we are back in the group buffer.
>
> 3) Very briefly the mini-buffer flashes: "Retrieving newsgroup:
> nnml:mail.misc" [this is my main inbox newsgroup]
>
> 4) The minibuffer queries how many articles.
>
> Is this different from your behavior?

Slightly, I'd say so. The group buffer is not entered resp. the summary
buffer not left here, afaik. But the complete article list is rebuilt,
that's right. So if you want old articles to stay in place and only 'add'
new ones, no I don't know how to accomplish this. Actually I'd be surprised
if this was possible.

On the other hand, I'm not sure why you'd want this (without questioning
that it might make sense for you). Since, as I'm reading through articles
myself, I type 'x' now and then to actually hide read articles until I'm
finished. Also, I'm very happy that Gnus doesn't pop in new articles now
and then like e.g. Evolution, since if you left articles unread while going
through the list just to do an all catch up 'c' at the end, with other
clients you'd never know whether you'd unwillingly catch up an article not
yet seen.

Anyway, regarding your particular issue I can be of no help I'm afraid .

Regards, Bruno.


  reply	other threads:[~2005-03-29 23:28 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 [this message]
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
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=m3r7hyxc9x.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).