Gnus development mailing list
 help / color / mirror / Atom feed
From: "Steven E. Harris" <seh@panix.com>
Subject: Re: nnimap problem solved by removing .agentview and .overview
Date: Tue, 17 Aug 2004 08:50:19 -0700	[thread overview]
Message-ID: <jk43c2lepc4.fsf@W003275.na.alarismed.com> (raw)
In-Reply-To: <ilupt5q2mwv.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> writes:

> The unread article count in group buffer is only an estimate.  In
> situations like this, it will be wrong.  But I thought there was
> some workaround for this.  What's the value of
> `gnus-after-getting-new-news-hook' for you?  It should include
> `gnus-fixup-nnimap-unread-after-getting-new-news'.

,----[ gnus-after-getting-new-news-hook ]
| `gnus-after-getting-new-news-hook' is a variable declared in Lisp.
|   -- loaded from "gnus-start"
| 
| Value: (gnus-display-time-event-handler gnus-fixup-nnimap-unread-after-getting-new-news)
| 
| Documentation:
| *A hook run after Gnus checks for new news when Gnus is already running.
`----

The fixup hook is in there, but it's not doing its job. I did note
that hitting M-g on the group before entering it fixes the
count. Perhaps this hook is not getting run upon initial connection.

> They are supposed to be stored on the server, if the server support
> client-specific flags.  Do (setq imap-log t) and look in *imap-log*
> buffer for the PERMANENTFLAGS value for the mailbox, e.g.:
>
> * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen NonJunk \*)]  
>
> The \* is the critical value.  If it is absent, Gnus cannot store
> non-standard flags on the server.

,----
| 187 EXAMINE "INBOX.lists.gnus-ding"
| * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)
| * OK [PERMANENTFLAGS ()] No permanent flags permitted
| * 29 EXISTS
| * 0 RECENT
| * OK [UIDVALIDITY 1067647543] Ok
| * OK [MYRIGHTS "acdilrsw"] ACL
| 187 OK [READ-ONLY] Ok
`----

Lovely. Is this something that I can appeal to my ISP's administrators
to enable, or is it an inherent feature lack in a given IMAP
implementation (in this case, Courier)?

Just to reiterate, though, .newsrc.eld is in fact quite necessary for
maintaining proper IMAP state if the server isn't as complicit as Gnus
would prefer. Perhaps we can move these nnimap marks out of
.newsrc.eld, or at least echo them into marks files like the NNTP
backends do.

-- 
Steven E. Harris



  parent reply	other threads:[~2004-08-17 15:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 21:36 Mats Lidell
2004-08-11 22:05 ` Steven E. Harris
2004-08-12  2:11 ` Kevin Greiner
2004-08-12 15:13   ` Steven E. Harris
2004-08-12 15:46     ` Simon Josefsson
2004-08-12 16:08       ` Steven E. Harris
2004-08-12 16:48         ` Simon Josefsson
2004-08-12 17:26           ` Steven E. Harris
2004-08-12 19:31             ` Simon Josefsson
2004-08-16 15:02               ` Steven E. Harris
2004-08-16 15:11                 ` Steven E. Harris
2004-08-16 15:31                 ` Simon Josefsson
2004-08-16 16:45                   ` Steven E. Harris
2004-08-16 16:59                     ` Simon Josefsson
2004-08-16 17:50                       ` gnus-parameters remodeled for Topics (was: nnimap problem solved by removing .agentview and .overview) Ted Zlatanov
2004-08-16 20:03                         ` gnus-parameters remodeled for Topics Steven E. Harris
2004-08-17  3:13                   ` nnimap problem solved by removing .agentview and .overview Steven E. Harris
2004-08-17  8:23                     ` Simon Josefsson
     [not found]                       ` <ilupt5q2mwv.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2004-08-17 11:59                         ` Jochen Küpper
2004-08-17 15:50                       ` Steven E. Harris [this message]
2004-08-17 16:40                         ` Simon Josefsson
2004-08-12 19:49       ` Mats Lidell
2004-08-12 20:35         ` Simon Josefsson
2004-08-20 22:09           ` Mats Lidell
2004-08-12 21:30       ` Kevin Greiner
2004-08-12 22:28         ` Simon Josefsson
2004-08-16 17:45       ` Ted Zlatanov
2004-08-16 18:34         ` Chris Green
2004-08-16 19:43           ` Steven E. Harris
2004-08-16 19:54         ` Steven E. Harris
2004-08-17 11:39         ` Steinar Bang

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=jk43c2lepc4.fsf@W003275.na.alarismed.com \
    --to=seh@panix.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).