From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Fetching Message-ID --> nnfolder
Date: Sun, 16 May 2004 14:59:41 +0200 [thread overview]
Message-ID: <m3ekpkil36.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <wk65c3d3h3.fsf@smsoft.ixy.de>
Michael Schierl <schierlm-usenet@gmx.de> writes:
> 1. Sometimes I get an error that article -1 cannot be copied (however,
> when I want to hunt it down, it does not appear, so I cannot
> provide an exact error message).
This usually happens when there's a dummy article, or an article
fetched by Message-ID present in the summary buffer.
> 2. I could not find a way to make the "copy" unread. When the article
> is moved, it remains unread as it should, but the copy will become
> read. (Since the "Original" will disappear when the group is
> exited, the only article remaining will be read).
> `gnus-preserve-marks' is `t'.
You could bind that variable to nil in your function.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-05-16 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 20:31 Michael Schierl
2004-05-16 12:59 ` Lars Magne Ingebrigtsen [this message]
2004-05-17 19:43 ` Michael Schierl
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=m3ekpkil36.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).