From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Setting Status header in nnml?
Date: 10 Feb 1999 11:38:07 -0500 [thread overview]
Message-ID: <lthfsu1afk.fsf@asfast.com> (raw)
In-Reply-To: Justin Sheehy's message of "10 Feb 1999 11:18:46 -0500"
Justin Sheehy <justin@linus.mitre.org> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
> > I'm wondering about the feasibility of an idea: could Gnus set the
> > `Status:' header to some sort of meaningful value(s) in the actual
> > message files when using the nnml back end? This way, some external
> > (i.e., non-Gnus) software could interrogate the new/read/unread/etc.
> > status of email in the various nnml directories I'm using.
> >
> > This would also be nice within the other back ends, as well, such as
> > nnfolder ... but perhaps this is already done in some of these ... ???
>
> Well, that information already exists. For example, you could just
> parse the ~/.newsrc.eld file.
I was hoping I wouldn't have to do that ... :):)
> Using Status headers in the way you describe might be possible, but
> would be really expensive. For instance, if you did a catchup on a
> group with many articles, Gnus would have to open each file and modify
> it. This could take a really long time.
Yeah ... I know. But perhaps this capbility could be an option for those
of us who want to pay the price in processing time. The default behavior
could be the same as what we have today.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~1999-02-10 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-10 16:11 Lloyd Zusman
1999-02-10 16:18 ` Justin Sheehy
1999-02-10 16:38 ` Lloyd Zusman [this message]
1999-02-10 19:59 ` Justin Sheehy
1999-02-11 0:05 ` Patrick Audley
1999-02-11 16:41 ` Justin Sheehy
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=lthfsu1afk.fsf@asfast.com \
--to=ljz@asfast.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).