From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
Subject: Re: mh backend
Date: Tue, 15 Sep 1998 18:43:52 -0400 [thread overview]
Message-ID: <199809152243.SAA25225@alderaan.gsfc.nasa.gov> (raw)
In-Reply-To: <oqpvcxf3fy.fsf@icule.progiciels-bpi.ca> (message from =?ISO-8859-1?Q?Fran=E7ois_Pinard?= on 15 Sep 1998 17:53:21 -400)
Excerpts from mail: (15-Sep-98) Re: mh backend by =?ISO-8859-1?Q?Fran=E7ois Pinard?=
>>>> 1. Message sequences.
>> In MH/nmh, you can give symbolic names to an arbitrary list of
>> numbers. Then you can manipulate the messages that these numbers
>> represent, by using the message sequence. [...]
This sounds a lot like RMAIL labels. I know that, at one point, adding
user-customizable labels or annotations to Gnus was on the to-do list, but
it's probably way down on the list.
> Could mailgroups, or submailgroups, be used to similar purposes? Maybe not,
> if a single message may be part of many sequences simultaneously. Let's
> assume for a moment it would be possible...
Someone invariably suggests that when the topic of Gnus labels comes up.
Personally, I think subgroups are a very poor alternative.
>> Well, it's common to repack the folder in the MH/nmh world. The message
>> numbers are not hidden in the background quite as much as in Gnus.
>
> Maybe (just hypothesising :-) because you often need to look at these
> numbers. If you stopped having this need, probably the need to repack
> would disappear as well?
I think it would be great if Gnus could count articles correctly. However,
someone may have already written a function to pack an nnml group. See the
the following articles on the Gnus mailing list archive:
<http://www.gnus.org/cgi-bin/wilma_glimpse/ding?query=function+to+pack+folders&Search=Search&lineonly=on&errors=0&maxfiles=50&maxlines=10&.cgifields=lineonly&.cgifields=filelist&.cgifields=case&.cgifields=partial&.cgifields=restricttofiles>
>> Yes, limiting takes care of matching on headers, but unless I'm
>> missing something obvious, one cannot limit based on the contents
>> message body.
> For one, I do it with temporary scoring instead. Maybe it would be
> convenient that have a limiting function for that as well? It might be
> slow.
I really think limiting on the body should be added as feature. (If it's not
already. I could have sworn it was!) It would be really useful, I think.
Later,
Ed
next prev parent reply other threads:[~1998-09-15 22:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-14 22:51 Phil Humpherys
1998-09-15 7:45 ` Kai Grossjohann
[not found] ` <87lnnl9msl.fsf@lemmon.iomega.com>
1998-09-16 7:31 ` Kai Grossjohann
1998-09-16 7:37 ` Phil Humpherys
[not found] ` <x7g1dtfibe.fsf@peorth.gweep.net>
1998-09-15 18:06 ` Rajappa Iyer
1998-09-15 19:32 ` François Pinard
1998-09-15 20:34 ` Richard Coleman
1998-09-15 21:53 ` François Pinard
1998-09-15 22:43 ` Edward J. Sabol [this message]
1998-09-22 15:43 ` Justin Sheehy
1998-09-22 15:59 ` Hrvoje Niksic
1998-09-22 16:18 ` Alan Shutko
1998-09-23 8:33 ` Kai Grossjohann
1998-09-23 15:44 ` Matt Pharr
1998-09-23 16:45 ` Kai Grossjohann
1998-09-16 15:06 ` Per Abrahamsen
1998-09-15 20:43 ` Rajappa Iyer
1998-09-15 21:47 ` Phil Humpherys
1998-09-16 8:03 ` Kai Grossjohann
1998-09-16 9:36 ` Lars Magne Ingebrigtsen
1998-09-15 21:39 ` David Hedbor
1998-09-16 8:06 ` Kai Grossjohann
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=199809152243.SAA25225@alderaan.gsfc.nasa.gov \
--to=sabol@alderaan.gsfc.nasa.gov \
/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).