> Public bug reported:
>
> I am seeing occasions where vm will save the inbox even though no
> changes are indicated.
I hope you don't mean that VM is saving the inbox on its own? That is
not supposed to happen.
If you mean that the buffer-modified-p flag is getting set needlessly,
that is possible. This is indicated by "*" or "**" in the modeline.
Ideally, all the three VM buffers (Folder, Presentation and Summary)
should show the same buffer-modified-p status. But they are going
their own ways, and it is hard to tell when the folder's status has
changed.
If you can find a reproducible sequence of actions that change the
buffer-modified-p flag needlessly, I can fix it. I myself don't use
IMAP spool files. So, I don't run into these problems.
John Hein writes:
> Public bug reported:
>
> I am seeing occasions where vm will save the inbox even though no
> changes are indicated.
I hope you don't mean that VM is saving the inbox on its own? That is
not supposed to happen.
If you mean that the buffer-modified-p flag is getting set needlessly,
that is possible. This is indicated by "*" or "**" in the modeline.
Ideally, all the three VM buffers (Folder, Presentation and Summary)
should show the same buffer-modified-p status. But they are going
their own ways, and it is hard to tell when the folder's status has
changed.
If you can find a reproducible sequence of actions that change the
buffer-modified-p flag needlessly, I can fix it. I myself don't use
IMAP spool files. So, I don't run into these problems.
Cheers,
Uday