From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: New marks stuff
Date: Sun, 19 Aug 2001 12:40:11 +0200 [thread overview]
Message-ID: <ilubslc2v04.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m1n14wgz4y.fsf@reader.newsguy.com> (Harry Putnam's message of "19 Aug 2001 03:10:13 -0700")
Harry Putnam <reader@newsguy.com> writes:
> Is the new Marks stuff wreaking havoc with any ones setup?
Seems that way. :-/
> Seems to have booggered up read unread. All new mail now arrives and
> never shows up as unread. When looking in the actual directory I see
> the new messages but gnus doesn't think they are new.
Do you see them marked as read in Gnus, or not at all?
Maybe you could try the edebug hint from my reply to Daniel.
next prev parent reply other threads:[~2001-08-19 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 10:10 Harry Putnam
2001-08-19 10:40 ` Simon Josefsson [this message]
2001-08-24 18:37 ` Bill White
2001-08-24 19:39 ` ShengHuo ZHU
2001-08-25 6:47 ` Karl Eichwalder
2001-08-27 16:14 ` Simon Josefsson
2001-08-27 20:36 ` Karl Eichwalder
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=ilubslc2v04.fsf@barbar.josefsson.org \
--to=jas@extundo.com \
--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).