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 09:31:39 +0200	[thread overview]
Message-ID: <m3d5thr3ms.fsf@caruso.quasi.local> (raw)
In-Reply-To: <86psxhhcu0.fsf@pallotta.studby.uio.no>

steinab@ifi.uio.no (Steinar Børmer) writes:

> I have no idea since `/ N' behaves like it should for me.  If new
> messages have arrived, they are inserted and the rest of the *Summary*
> buffer is unchanged.  If no new messages have arrived, gnus responds
>
> "No gnus is bad news".
>
> The *Summary* buffer is not changed at all.
>
> Are you certain you haven't set any variables that influence this?

Maybe it's backend specific (?) I checked that function/key some time ago
on nnimap backends, but it didn't seem to work. Checked again now, and this
time it does, i.e. /N really fetches new articles from my imap server
without completely rebuilding the summary buffer. Cool so far.

On the other hand, the following snippet from the info manual

 `/ N'
     Insert all new articles in the summary buffer.  It scans for new
     emails if BACK-END`-get-new-mail' is non-`nil'.

is somehow confusing since I've never set nnimap-get-new-mail, nor is it
referenced in any of the Gnus lisp files. So could be some backends need it
and others not. Maybe setting that variable changes the /N behavior for OP?

Regards, Bruno.


  reply	other threads:[~2005-03-30  7:31 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 [this message]
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=m3d5thr3ms.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).