Move articles while offline

Move articles while offline

[Kai Großjohann]

I'd like to start a discussion on how to implement moving articles
while offline.  What features do you want to see?  Is it necessary to
be fully transparent?

One part that I'm fairly sure about is that moving article 4711 while
offline should make a note about the source group, the source article
number, and the target group, in the list of things to do when
synchronizing.  (Perhaps together with the flags synchronization
stuff.)

Of course, if uidvalidity changes when you plug in again, you're
screwed.  How does the flags sync code do this?

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

Re: Move articles while offline

[Simon Josefsson]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> One part that I'm fairly sure about is that moving article 4711 while
> offline should make a note about the source group, the source article
> number, and the target group, in the list of things to do when
> synchronizing.  (Perhaps together with the flags synchronization
> stuff.)

Another step is to make the newly moved article visible offline, as it
had already been transfered to the server.  This is more difficult,
but I think people kind of expect this to work.  OTOH it is probably
best to leave this until the low-level stuff works.

> Of course, if uidvalidity changes when you plug in again, you're
> screwed.  How does the flags sync code do this?

It doesn't. :-/

Re: Move articles while offline

[Kai Großjohann]

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?

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

Re: Move articles while offline

[Simon Josefsson]

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.