Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: johnsu01 <x@x.x>
Subject: Re: What 'g' does
Date: Tue, 02 Mar 2004 07:08:04 GMT	[thread overview]
Message-ID: <87y8qjep84.fsf@ohara.isa-geek.net> (raw)
In-Reply-To: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87hdx97dmp.fsf@gothgoose.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcus Frings <iam-est-hora-surgere@despammed.com> writes:

> * johnsu01 <x@x.x> wrote:
>
>> Why is it that when I hit "g" to get all the new messages, Gnus
>> doesn't actually check for new mail? I have to go to each individual
>> group and hit alt-g in order to get the new messages for that group. I
>> am just using it to read email, using nnml as a backend. The mail is
>> brought in from my /var/mail spool. The new mail indicator seems to be
>> working properly. Any ideas what variable I have to define or setting
>> I have to change? I can't figure out what I have done differently in
>> this gnus setup from what I have done in others.
>
> <http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&oe=UTF-8&selm=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87wu7odgf7.fsf%40gothgoose.net&rnum=3>
>
> Regards,
> Marcus
> -- 

My German is not very good.

The link didn't work. Brought up a Google error message (auf
Deutsch). 

But, I solved the problem by changing the names of my mail groups to
remove the nnml: from them. After that, no problem. 







-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFARCnHCRwR0q6GALYRArN1AKCpkGEvPVEAgyggRSjWqszTQ0Kc5gCgrKww
kfU3w15p9ajzEDch4s2ntr8=
=fuHz
-----END PGP SIGNATURE-----


           reply	other threads:[~2004-03-02  7:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87hdx97dmp.fsf@gothgoose.net>]

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=87y8qjep84.fsf@ohara.isa-geek.net \
    --to=x@x.x \
    /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).