VM

Comment 2 for bug 703775

Revision history for this message
Tim Cross (tcross) wrote : Re: [Bug 703775] [NEW] Message indicagtor and cursor not moving in sync in summary buffer

On Tue, Jan 18, 2011 at 1:48 AM, Uday Reddy <email address hidden> wrote:

> I couldn't reproduce it on a couple of Emacs24 versions I tried,
> including the 20110110 build on Windows.
>
> Can you reproduce it with the default settings of VM?
>
> Cheers,
> Uday
>
> I have reduced my configuration to the bare minimum and the problem still
persists, though it is slightly modified and this has given some more
information.

Given the below summary buffer layout (slightly edited to protect the
guilty) where -> is the message indicator and ^ is the emacs cursor

  176 Raelene xxxx Jan 17 257/14553 ""
  177 Grant xxxx Jan 17 84/3320 "Windows Oncall."
  178 Brendan xxxxxxx Jan 12 374/21860 "Unicon, CAS and Shiboleth"
^->179 R To: Brendan xxxxx Jan 17 129/4823 "Unicon, CAS and Shiboleth"
  180 D Tim xxxxx Jan 17 46/1321 "Unicon, CAS and Shiboleth"
  181 U To: Tim xxxxx, Br Jan 17 46/1321 "Unicon, CAS and Shiboleth"
  182 N Tim xxxxx Jan 17 43/1250 "emacspeak-bmk-mgr
vanished?"

If I hit 'p', both the cursor and the -> will be moved to message 178 and
the message will display correctly. Hitting 'p' a second time will move to
message 177 as expected - all seems OK. However, if I now hit 'n',
everything moves to 178 as would be expectred, a second 'n' moves to 179,
looking good. Now, hitting 'n' for a thrid time and the problem is again
evident. The -> message indicator jumps to message 181, skipping the deleted
message 180, but the cursor stays on message 179. Hitting 'n' again and
neither moves - the message indicator stays at 181 and the cursor stays at
179. If I hit 'space' to display the message, the -> message indicator jumps
back to message 179 and that message is revealed.

The problem appears to be related to the 'U' and 'N' indicator i.e. unread
and new messages. If I use C-n to move to messages 181 and 182, hitting
space then reveals the contents of these messages. As they have now been
read, the 'U' and 'N' markers are removed and now I can move up/down with p
or n.

My vm config consists only of

; General settings
(setq vm-window-configuration-file "~/.vm.windows"
      vm-crash-box "/home/tcross/Mail-VM/INBOX.crash"
      vm-folder-directory "~/Mail-VM/"
      vm-primary-inbox "/home/tcross/Mail-VM/INBOX"
      vm-spool-file-suffixes '(".spool")
      vm-spool-files '(("/home/tcross/Mail-VM/INBOX"
                        "/home/tcross/Mail-VM/NEWMAIL"
                        "/home/tcross/Mail-VM/INBOX.crash")))

; MIME decode/encode helpers
(setq vm-mime-base64-decoder-program "/usr/bin/perl"
      vm-mime-base64-decoder-switches
      '("-MMIME::Base64" "-ne" "print decode_base64($_)")
      vm-mime-base64-encoder-program "/usr/bin/perl"
      vm-mime-base64-encoder-switches
      '("-MMIME::Base64" "-ne" "print encode_base64($_)")
      vm-mime-qp-decoder-program "/usr/bin/perl"
      vm-mime-qp-decoder-switches
      '("-MMIME::QuotedPrint" "-ne" "print decode_qp($_)")
      vm-mime-qp-encoder-program "/usr/bin/perl"
      vm-mime-qp-encoder-switches
      '("-MMIME::QuotedPrint" "-ne" "print encode_qp($_)"))

Emacs version is
GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.22.0) of 2011-01-17
on blind-mole

VM was updated from the bzr trunk yesterday and reports as 8.1.93a

Tim