Gnus development mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <schwinge-lists-gnus.org-ding@nic-nac-project.de>
Subject: Re: nnmaildir
Date: Fri, 13 Feb 2004 15:02:15 +0100	[thread overview]
Message-ID: <20040213140215.GA15488@server.schwinge.homeip.net> (raw)
In-Reply-To: <m3lln7dhye.fsf@multivac.cwru.edu>

On Thu, Feb 12, 2004 at 05:56:45PM -0500, Paul Jarc wrote:
> Thomas Schwinge <schwinge-lists-gnus.org-ding@nic-nac-project.de> wrote:
> > So the error is likely be somewhere in the code that recognises new
> > folders and adds them to the group buffer.
> 
> Ok... try opening the *Server* buffer (type [^] from the *Group*
> buffer) and enter the nnmaildir server.  Then switch to the " *nntpd*"
> buffer (note the leading space).  See how the group names show up
> there - that will at least tell us whether the problem is inside
> nnmaildir or outside.

#v+
[...]
lists.skarnet\.org.supervision 46 1 y
lists.gnus\.org.ding 38 1 y
INBOX 26 1 y
[...]
#v-

This is correct whereas it's incorrent when browsing the nnmaildir
server:
#v+
[...]
      38: lists.gnus.org.ding
      72: lists.isdn4linux.de.isdn4linux
     131: lists.multivac.cwru.edu.prjware
[...]
#v-


> >> But there is another way we can arrive at this same situation: suppose
> >> a message initially has neither 'tick or 'dormant, and the user adds
> >> 'dormant.
> >
> > Additionally nnmaildir will set 'F'.
> 
> Ok, that would remove the ambiguity.  But even so, I'd rather keep it
> simple, and have "F" correspond exactly to 'tick.

I wouldn't, but of course that's less urgent than getting the whole
thing working at all.

Regards,
 Thomas



  reply	other threads:[~2004-02-13 14:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 17:00 nnmaildir Thomas Schwinge
2004-02-11 17:42 ` nnmaildir Paul Jarc
2004-02-11 22:05   ` nnmaildir Thomas Schwinge
2004-02-11 23:23     ` nnmaildir Paul Jarc
2004-02-12 14:35       ` nnmaildir Thomas Schwinge
2004-02-12 16:36         ` nnmaildir Paul Jarc
2004-02-12 22:45           ` nnmaildir Thomas Schwinge
2004-02-12 22:57             ` nnmaildir Paul Jarc
2004-02-13 14:02               ` Thomas Schwinge [this message]
2004-02-14  3:34                 ` nnmaildir Paul Jarc
2004-02-14 18:26 ` nnmaildir Kai Grossjohann
2004-02-14 18:38   ` #v+, #v- (was: nnmaildir) lawrence mitchell
2004-02-14 22:18     ` #v+, #v- Kai Grossjohann
2004-02-15  3:33       ` Karl Pflästerer
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22 23:33 db-backed mail back end Lars Magne Ingebrigtsen
2002-01-23  0:23 ` Daniel Pittman
2002-01-23  0:36   ` Lars Magne Ingebrigtsen
2002-01-24  0:50     ` Russ Allbery
2002-01-24  1:24       ` Lars Magne Ingebrigtsen
2002-01-24 17:11         ` Paul Jarc
2002-01-24 17:58           ` nnmaildir (was: db-backed mail back end) Josh Huber
2002-01-24 18:14             ` Harry Putnam
2002-01-24 18:43               ` Paul Jarc
2002-01-24 22:05                 ` Harry Putnam
2002-01-24 22:51                   ` nnmaildir Paul Jarc
2002-01-24 18:39             ` nnmaildir Paul Jarc

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=20040213140215.GA15488@server.schwinge.homeip.net \
    --to=schwinge-lists-gnus.org-ding@nic-nac-project.de \
    /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).