Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: going imap
Date: Tue, 13 May 2003 13:29:19 +0200	[thread overview]
Message-ID: <iluof27nkz4.fsf@latte-wlan.josefsson.org> (raw)
In-Reply-To: <87smrjw8t7.unregulated@boppy.dyndns.org>

Paul Stevenson <paul@gleet.org.uk> writes:

> Hello,
>   I decided it was time to read my mail via imap, since it is the
>   'supported' way to do it here.  In fact the local imap system writes
>   files directly to ~/mbox (which is how I slurped the mail before)
>   and also sometimes directly into ~/Mail (there is some splitting of
>   spam before the mail gets to me),  which was not really good,  but
>   we are supposed to read these files through imap.   
>
>   Anyway, because of the second point,  I set gnus-home-directory to
>   be something new in my .emacs file and began affresh with a very
>   clean .gnus with just 
>
> (setq gnus-select-method
>       '(nnimap "mail"
>                (nnimap-address "imap.server")
>                                (nnimap-list-pattern ("INBOX" "Mail/*"))))
>
>   since I don't want to read netnews from this account.  
>
>   So, things kinda work except that when I start up a gnus session,
>   gnus doesn't know how many unread articles are in the nnimap groups
>   as viewed from the group buffer.  Only after looking at an nnimap
>   group do I get an unread article count.  The information is then
>   lost between gnus sessions.
>
>   Also 'g' doesn't see new mail.  M-g does, but I don't want to have
>   to position the cursor over my INBOX group before I can hit some key
>   to check for new mail.   

Does setting `nnimap-need-unselect-to-notice-new-mail' help?

>   Are these just features of imap that I will learn to live with?

It works for me.


  reply	other threads:[~2003-05-13 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  8:27 Paul Stevenson
2003-05-13 11:29 ` Simon Josefsson [this message]
     [not found]   ` <87llxbvzjq.semiexecutive@boppy.dyndns.org>
2003-05-13 12:11     ` Kai Großjohann
     [not found] ` <843cjjf585.fsf@lucy.is.informatik.uni-duisburg.de>
2003-05-13 12:51   ` Paul Stevenson
2003-05-13 16:36     ` Simon Josefsson
     [not found]     ` <84fznjxamc.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]       ` <u65nkfp6i.fsf.Hubert.Canon@alussinan.org>
     [not found]         ` <8465nhoqb1.fsf@lucy.is.informatik.uni-duisburg.de>
2003-06-10 10:33           ` Hubert Canon
     [not found]             ` <84smqiw4pn.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]               ` <uhe6xrhwy.fsf.Hubert.Canon@alussinan.org>
     [not found]                 ` <ubrx3k4q9.fsf.hcanon@alussinan.org>
     [not found]                   ` <724r2v6xn1.fsf@tindved.ii.uib.no>
     [not found]                     ` <84llw679jq.fsf@lucy.is.informatik.uni-duisburg.de>
2003-06-14 11:55                       ` Helge Avlesen
     [not found]                         ` <84he6s2yb7.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]                           ` <7265n7aaot.fsf@tindved.ii.uib.no>
2003-06-15 12:03                             ` Kai Großjohann

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=iluof27nkz4.fsf@latte-wlan.josefsson.org \
    --to=jas@extundo.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).