← Back to team overview

vm team mailing list archive

[Bug 498321] Re: vm-save-folder should always synchronize an imap folder, even if local buffer is not modified

 

Unfortunately, the version 8.0.14 is not "current".  It is at least one
year old, probably two.  Its IMAP support is 10 years old, basically
what Kyle Jones did just before he signed off!

You didn't say whether you are using 'IMAP folders' (which work quite
differently from local file system folders).  If you do vm-save-folder
on an IMAP folder then it will call vm-imap-synchronize-folder, not
otherwise.  My memory is that Kyle Jones's code for IMAP was kind of
half-done.  I couldn't really use it.

Once again, you will be better off waiting for the 8.1.0-beta release
this weekend.

Cheers,
Uday


** Changed in: vm
       Status: New => Incomplete

** Changed in: vm
     Assignee: (unassigned) => Uday Reddy (reddyuday)

-- 
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: Incomplete

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.





References