I've been stepping through execution of VM 8.2.0b1 function
"vm-attach-message" with edebug. I've also done the same with the VM
8.1.1 function "vm-mime-attach-message".
In VM 8.2.0b1 function "vm-attach-message" the "(interactive" clause
contains a "(cond" structure & both clauses in that have the clause
(setq mlist (vm-select-operable-messages 1 t "Attach"))
While stepping, I note that this clause gives a non-null value to
mlist and that means that the following "(when (null mlist)" isn't
satisfied and I don't get asked for a message number.
Equivalent logic in the VM 8.1.1 function "vm-mime-attach-message" has
Alan Wehmann continues:
I've been stepping through execution of VM 8.2.0b1 function attach- message" .
"vm-attach-message" with edebug. I've also done the same with the VM
8.1.1 function "vm-mime-
In VM 8.2.0b1 function "vm-attach-message" the "(interactive" clause
contains a "(cond" structure & both clauses in that have the clause
(setq mlist (vm-select- operable- messages 1 t "Attach"))
While stepping, I note that this clause gives a non-null value to
mlist and that means that the following "(when (null mlist)" isn't
satisfied and I don't get asked for a message number.
Equivalent logic in the VM 8.1.1 function "vm-mime- attach- message" has
(setq mlist (vm-select- marked- or-prefixed- messages 0))
and when stepping through that, mlist is returned as nil and the test
"(if (null mlist)" is successful and I get asked for a message
number.