Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: nnmaildir oddities!
Date: Thu, 18 Jul 2002 13:57:50 -0400	[thread overview]
Message-ID: <87ofd4hqap.fsf@mail.paradoxical.net> (raw)
In-Reply-To: <m3r8i17ykl.fsf@multivac.cwru.edu>

prj@po.cwru.edu (Paul Jarc) writes:

> Does (setq nnmaildir-get-new-mail t) help?

I think it gets a little better...

But, it still gets spooled to the sent-mail folder.  I see this in the
message buffer:

Saving to: nnmaildir: (31)... 

>> 2. Messages saved to the sent-mail folder (which are actually sent
>> mail) are not marked as read, even though I have gnus-gcc-mark-as-read
>> set.
>
> gnus-inews-do-gcc is supposed to take care of this:
> 	      (when (and group-art
> 			 (or gnus-gcc-mark-as-read
> 			     gnus-inews-mark-gcc-as-read))
> 		(gnus-group-mark-article-read group (cdr group-art)))
>
> If you debug-on-entry gnus-group-mark-article-read, is it called?  If
> not, you could debug nnmaildir-request-accept-article and make sure it
> returns a non-nil value (which is stored in group-art above, I think).

Ah -- I think I know the cause of my problems, perhaps.  I'm using
nnmaildir as my primary select method, is this not supported?

gnus-group-mark-article-read is trying to mark an article in
nnmaildir:sent-news, and there is no such group.  It's just
"sent-news"

> You should probably set gnus-uncacheable-groups to include
> "\\`nnmaildir[:+]" for now; nnmaildir article numbers are not quite
> persistent yet.

Okay, turning of the cache got rid of another problem I just noticed
-- the summary buffer lines not matching up with what was displayed in
the article buffer.

I'd really like to use this as my primary select method, since 99% of
my groups are mail.

Any thoughts?

-- 
Josh Huber



  reply	other threads:[~2002-07-18 17:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 16:34 Josh Huber
2002-07-18 17:08 ` Paul Jarc
2002-07-18 17:57   ` Josh Huber [this message]
2002-07-18 18:21     ` Paul Jarc
2002-07-18 18:41       ` Josh Huber
2002-07-18 19:17         ` Paul Jarc
2002-07-18 20:16           ` Josh Huber
2002-07-18 20:26             ` Paul Jarc
2002-07-18 20:42               ` Josh Huber
2002-07-18 20:59                 ` Paul Jarc
2002-07-18 21:27                   ` Josh Huber
2002-07-18 21:32                     ` Paul Jarc
2002-07-19  7:23                     ` Kai Großjohann
2002-07-19 19:34                       ` Josh Huber
2002-07-26 19:32                         ` Simon Josefsson
2002-07-26 20:06                           ` Josh Huber
2002-07-26 20:33                             ` Simon Josefsson
2002-07-26 20:44                               ` Paul Jarc
2002-07-26 21:01                                 ` Josh Huber
2002-07-26 22:40                                   ` Simon Josefsson
2002-07-26 21:03                                 ` Simon Josefsson

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=87ofd4hqap.fsf@mail.paradoxical.net \
    --to=huber@alum.wpi.edu \
    /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).