Re: Move articles while offline

[Simon Josefsson <jas@extundo.com>]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> One idea for implementing $SUBJECT is to save to-be-moved articles as
> drafts.  That is, when you hit B m on an article while offline, the
> article is fetched, some headers are added, and then it is saved in
> nndraft:queue.
>
> The new headers would prevent gnus-group-send-queue from doing their
> normal operation.  Instead, they would save the article in the group
> indicated by a special header (the Gcc header comes to mind), and
> then they would set marks on the new article.  (The marks would be
> indicated in one of the new headers.
>
> So it seems that just a single header along the lines of
>
>     X-Gnus-Move-Flags: (ticked)
>
> could be sufficient.  The Gcc header indicates the target group.
>
> The same machinery could be used for auto-marking other Gcc'd
> articles.
>
> Thoughts?

Looks good.  Maybe place the offline-moved articles in its own
nndraft: folder?  Then it might be easier to locate the message and
insert them into the appropriate group while offline, to give the
impression that the article was already moved.  Hm.  Another idea: how
about using the cache to simulate that articles exist in the group?
Then the code to handle overview data and group high/low article count
and summary insertion already exists.  Only problem is which article
number to use.  Maybe negative ones work.