From: steve@miranova.com (Steven L. Baur)
Subject: Re: Default save-name for saving news articles
Date: 13 Nov 1995 10:03:03 -0800 [thread overview]
Message-ID: <m2ka54qtns.fsf@diana.miranova.com> (raw)
In-Reply-To: Per Abrahamsen's message of 13 Nov 1995 06:24:44 -0800
>>>>> "Per" == Per Abrahamsen <abraham@dina.kvl.dk> writes:
>>>>> "SLB" == Steven L Baur <steve@miranova.com> writes:
SLB> When saving articles from News, I save them to my incoming
SLB> procmail spool directory, so that Gnus can take them and do
SLB> whatever it has to do to keep the nnml NOV files up to date.
Per> Why don't you just use `B m' to move the message?
``The current newsgroup does not support article moving''
Even if it did work, it does not have the desired semantics. I like
the feature that saving the article leaves it unread in the
destination folder. B m has three flaws: (sgnus 0.12)
* It does not respect readedness status of the starting article. It
usually leaves the article read.
* Sometimes it does not leave the article read, but the group listing
is not updated properly. I haven't tracked this down enough to make
a decent bug report yet.
* It does not copy status. Eg. a marked article (with ``!'') does
not end up marked in the destination folder. I haven't checked
fully, but I don't believe it copies things like reply status either.
You could also add the number of keystrokes required too.
B m nnml:news.group <RET> -vs-
o <RET>
Per> Saving them in your incomming procmail spool directory could
Per> cause problems (like lost mail) if procmail is also
Per> delivering a messages there.
I have multiple spool files there. How can writing to
gnu.emacs.gnus.spool cause mail lossage when procmail does not know
about that file?
--
steve@miranova.com baur
next reply other threads:[~1995-11-13 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-13 18:03 Steven L. Baur [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-11 22:38 Steven L. Baur
1995-11-12 1:58 ` Robert Nicholson
1995-11-13 22:48 ` Lars Magne Ingebrigtsen
1995-11-13 14:24 ` Per Abrahamsen
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=m2ka54qtns.fsf@diana.miranova.com \
--to=steve@miranova.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).