Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Support moving articles in Agent?
Date: Sun, 06 Oct 2002 10:16:27 +0200	[thread overview]
Message-ID: <878z1ct21w.fsf@crybaby.cs.uni-dortmund.de> (raw)
In-Reply-To: <iluheg01jvn.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> writes:

> Make nnagent remember data in calls to e.g. request-move-article and
> invoke it when plugging back in (see `nnagent-request-set-mark' for an
> approach to achieve this).  One problem is, which article number do
> you assign new articles?  If the backend is e.g. nnimap, you cannot
> simply pick one (since the server decides this) unless you do
> something clever.  Using negative article numbers might work though,
> although you must make sure moving the same article several times
> between groups while unplugged doesn't make Gnus do strange things.

Maybe a first approach would be to leave the articles where they are
and just remember that they have been moved.  So the user types `B m'
on a message and the summary line changes somehow to indicate this,
but otherwise nothing obvious happens.  Then, when synchronizing
flags, Gnus really moves the message.

Another possibility might be to pseudo-insert the message into the
target group while unplugged.  For crossposted articles, it is
already possible for `^' to display an article in a group which
doesn't actually occur there.  Maybe a similar mechanism could be
used to display moved-while-offline articles in the target group.
What do you think?

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)



      reply	other threads:[~2002-10-06  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 21:32 Kai Großjohann
2002-10-06  0:38 ` Simon Josefsson
2002-10-06  8:16   ` Kai Großjohann [this message]

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=878z1ct21w.fsf@crybaby.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).