🚀 go-pugleaf

Robert Marshall <spam@chezmarshall.freeserve.co.uk> writes:

> The documentation for this says
>
>     Does nothing except insure that the next VM command will operate only
>     on the marked messages in the current folder.  This only works for
>     commands bound to key, menu or button press events.  M-x vm-command will
>     not work.
>
> However if there's an inadvertent mouse event the setting for the next
> command gets lost - which if you're about to (for example) send a
> digest and end up with the entire inbox in the digest it can take a
> while :-(
>
> I have sloppy focus the mouse strayed out of the window into another
> vm folder window and the vm-next-command-uses-marks was gone.
>
> Also the same problem if you use mouse-autoselect-window and can't remember 
> the key binding and then try to access to command off the menu...
>
> Using RobertF's patched version....
> not sure there's a lot that can be done about this though?

Not something like a simple bugfix.  It uses the variable
`last-command' and checks of it are everywhere ...

It should not happen if you use a WM with focus follows mouse or
preserve the last-command by a advice, e.g. on mouse-track if you
have a focus-on-click config or what ever command changes
last-command..

(defadvice mouse-track (around vm-next-command-uses-marks-fix activate)
  (let ((vm-next-command-uses-marks-fix last-command))
    (message "last-command = %S <<" last-command)
    ad-do-it
    (if (eq vm-next-command-uses-marks-fix 'vm-next-command-uses-marks)
        (setq this-command 'vm-next-command-uses-marks))))

Robert