Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Packing nnml folders...
Date: 28 Jul 2001 17:37:08 -0400	[thread overview]
Message-ID: <yge8zh8spkr.fsf@asfast.com> (raw)
In-Reply-To: <vafvgkcwy2g.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 28 Jul 2001 23:20:07 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> On 28 Jul 2001, Lloyd Zusman wrote:
> 
>> The original poster asked for the numbers to start at 1.  I also
>> have a desire for the numbers to start at 1.  I understad that for
>> you, it isn't necessary for the numbers to start at 1, and so
>> therefore, much of this discussion probably doesn't pertain to you.
> 
> Hm.  Hmmmm...
> 
> *innocent look*
> 
> Why is it useful to have the numbers start at one?

I can't speak for the original poster, but for me, the reason is this:
I have utilities that operate outside of Gnus that do various things
to certain lists of pre-received messages that I keep.  I find Gnus
and nnml to be particularly useful for managing this list of messages,
because then each one of them resides in a nice, uniquely named file
in a known directory.  I find it quite desirable and convenient for
these utilities of mine to always operate on a set of messages whose
file names consist of a monotonically increasing sequence of numbers
that begin with 1.

I don't want this for all my nnml groups, but for a select subset that
has importance to me.

For me, this is more than enough reason to want a more convenient way
to maintain this list of messages whose numbers are packed and start
at 1.  Up until now, I didn't discuss this in this group, however,
because it seemed to be of idiosyncratic interest to only myself.  But
now that others have started talking about wanting, each for his or
her own reasons, to number certain lists of messages in the same way,
it seems to me that it has become appropriate for me to contribute my
ideas to this thread.

And by the way ... even as we speak (er, write), I'm in the process of
writing a function that will renumber nnml groups in this exact
manner.  I will post it here for discussion once I'm finished.
Perhaps some people besides me will find it to be useful.


> kai
> -- 
> ~/.signature: No such file or directory
> 

-- 
 Lloyd Zusman
 ljz@asfast.com


  reply	other threads:[~2001-07-28 21:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-27 17:17 Jon Allen Boone
2001-07-27 20:22 ` Kai Großjohann
2001-07-28  0:47   ` Lloyd Zusman
2001-07-28  1:43     ` Jon Allen Boone
2001-07-28  2:13       ` Paul Jarc
2001-07-28  3:12         ` Jon Allen Boone
2001-07-28  6:30           ` Paul Jarc
2001-07-28 11:31           ` Kai Großjohann
2001-07-28 16:08             ` Lloyd Zusman
2001-07-28 18:38               ` Kai Großjohann
2001-07-28 19:02                 ` Lloyd Zusman
2001-07-28 21:20                   ` Kai Großjohann
2001-07-28 21:37                     ` Lloyd Zusman [this message]
2001-07-28 21:04               ` Paul Jarc
2001-07-29  2:18                 ` Lloyd Zusman
2001-07-29 19:01                   ` Lloyd Zusman
2001-07-29 20:58                   ` Kai Großjohann
2001-07-29 22:40                     ` Lloyd Zusman
2001-07-28 11:28     ` Kai Großjohann

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=yge8zh8spkr.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).