From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: new marks code is breaking a pre_marks setup
Date: Thu, 23 Aug 2001 13:33:23 +1000 [thread overview]
Message-ID: <873d6jsb5o.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <ysd6r8u3rchg.fsf@sol-cmarquar.pet.usa.alcatel.com> (Colin Marquardt's message of "Wed, 22 Aug 2001 14:50:03 -0700")
On Wed, 22 Aug 2001, Colin Marquardt wrote:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>> With the new marks code, you can move a directory like
>> ~/Mail/mail/misc from one machine to the other and the marks will go
>> along. Or you can save some of your mail groups on CD and then access
>> them later on, keeping all the marks and stuff.
>>
>> Previously, all the marks were in .newsrc.eld, and it wasn't easy to
>> back up only that part of it which was relevant to a specific group.
>
> Cool. So SOUP is not really necessary anymore (not to mention that I
> never got it to work), or its function could change to only compress
> the stuff...
Actually, there are presumably still a few die-hard Fido Technology
Network users out there who use SOUP for access to Internet email and
all; I know that I did for a while when I was dealing primarily with FTN
mail...
...and SOUP keeps that information it's own way and interoperates with
other tools that speak it.[1] :)
Daniel
Footnotes:
[1] Well, I know of three -- the SOUP packager I had, GoldEd and Gnus. :)
--
You come for me now with a cake that you've made
Ravaged avenger with a clip in your hair
Full of glass and bleach and my old razorblades
O where do we go now but nowhere
-- Nick Cave, _Where Do We Go Now But Nowhere?_
next prev parent reply other threads:[~2001-08-23 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 20:52 Harry Putnam
2001-08-21 22:03 ` Harry Putnam
2001-08-21 22:12 ` Lars Magne Ingebrigtsen
2001-08-22 16:26 ` Kai Großjohann
2001-08-22 21:50 ` Colin Marquardt
2001-08-23 3:33 ` Daniel Pittman [this message]
2001-08-23 7:43 ` 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=873d6jsb5o.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).