vm team mailing list archive

[Uday Reddy <u.s.reddy@xxxxxxxxxxxxx>]

Good.  Thanks for checking it so quickly.  The principle used in VM is
that 'g' transfers information from the server to VM, and "S' transfers
information from VM back to the server.  vm-imap-synchronize does the
transfer in both directions.

(The only exception is that changed attributes are written to the server
during 'g'.  They are liable to get lost otherwise.  For instance,
suppose you undelete a message in VM, but it stays deleted on the
server.  If you download the deleted attribute and transfer it to the VM
folder, the user is likely to be surprised!)

All this is specified in the manual under "Server Folders".

There is no effort to keep the VM folder constantly in sync with the
server.  People thought it would be too confusing to see messages
disappear in the middle of reading them.

Cheers,
Uday


** Changed in: vm
       Status: Incomplete => Fix Released

** Changed in: vm
    Milestone: None => 8.1.0-beta

-- 
vm-save-folder should always synchronize an imap folder, even if local buffer is not modified
https://bugs.launchpad.net/bugs/498321
You received this bug notification because you are a member of VM
development team, which is the registrant for VM.

Status in VM (View Mail) for Emacs: Fix Released

Bug description:
Currently (vm 8.0.14) vm-save-folder appears to actually do a vm-imap-synchronize-folder if the folder is in fact accessed via imap.  This is good, since another mail client could have changed the folder on the imap server (e.g. deleted some messages), and this gives a mechanism for vm to update its view of the folder to reflect the server changes.

The issue is that vm-save-folder shortcuts and will not vm-imap-synchronize-folder if the buffer containing the folder is not currently modified (buffer-modified-p).  But it is entirely possible for the buffer to be unmodified but still out of sync due to changes only on the server.

vm-imap-synchronize-folder is not written as an interactive function so the best way I understand how to trigger it is via vm-save-folder.

As a workaround, I disabled the buffer-modified-p check in vm-save, and it seems to be working, though this is probably not the ideal fix.