From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: nnmaildir
Date: Wed, 11 Feb 2004 12:42:45 -0500 [thread overview]
Message-ID: <m365edwlzo.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <20040211170004.GA1389@server.schwinge.homeip.net> (Thomas Schwinge's message of "Wed, 11 Feb 2004 18:00:04 +0100")
Thomas Schwinge <schwinge-lists-gnus.org-ding@nic-nac-project.de> wrote:
> although I was not able to enter the ones whose are containing a
> '\': The were refused with:
> #v+
> Retrieving newsgroup: nnmaildir+nic-nac-project:lists.gnus.org.ding...
> gnus-select-newsgroup: Couldn't activate group nnmaildir+nic-nac-project:lists.gnus.org.ding: No such group: lists.gnus.org.ding
> #v-
I'm not sure what's happening here. It works for me, with a CVS
checkout from 2004-01-25. What version of Gnus are you using?
You could work around it by making a new directory for nnmaildir to
look at, which would contain symlinks to the actual maildirs. The
symlink names could omit "\".
> The issue remaining to be resolved for me is that I'd like to have the
> status flags synchronized between Gnus and the maildirs
You might find this useful for now:
http://article.gmane.org/gmane.emacs.gnus.general/55100
> I was not yet able to figure out which of the possible marks from
> <URL:http://www.gnus.org/manual/gnus_64.html> are actually used and
> stored on disk by nnmaildir
The ones I know of are 'dormant, 'expire, 'forward, 'read, 'reply,
'save, and 'tick. Note that there is no one-to-one correspondence
between the "marks" that appear in the user interface and the "marks"
that are stored persistently (either by Gnus or by a specific
backend). For example, "r", "R", and "O" are all represented by the
'read mark in the persistent storage.
> for the others (dormant, ...) we could either try to convince DJB
> to add them to the specification or the 'experimental semantics'
> described above could be used.
The experimental semantics wouldn't be useful; that would mean that
the message's info would look like ":1,..." which other MUAs wouldn't
understand.
paul
next prev parent reply other threads:[~2004-02-11 17:42 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 ` Paul Jarc [this message]
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 ` nnmaildir Thomas Schwinge
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=m365edwlzo.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=ding@gnus.org \
/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).