[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [VM] Trivial bugs in vm-8.2.0b

From: John Stoffel
Subject: Re: [VM] Trivial bugs in vm-8.2.0b
Date: Tue, 23 Jul 2013 11:11:13 -0400

>>>>> "Rainer" == Rainer Woitok <address@hidden> writes:

Rainer> Then I found out that I could not start writing a mail by
Rainer> hitting "m" (M-x vm-mail) because function
Rainer> "vm-select-recipient-from-sender" was un- defined.  I remedied
Rainer> this by doing:

Rainer> --- vm-reply.el.~1~     2011-12-28 00:19:28.000000000 +0200
Rainer> +++ vm-reply.el 2013-07-21 19:11:19.952000000 +0200
Rainer> @@ -1643,6 +1643,7 @@
Rainer>    (add-hook 'vm-mail-send-hook 'vm-forget-composition-buffer nil t)
Rainer>    (vm-update-ml-composition-buffer-count))
Rainer> +;;;###autoload
Rainer>  (defun vm-select-recipient-from-sender ()
Rainer>    "Select a recipient's address from the current message's sender, if
Rainer>  there is a current message."

Rainer> These all  are so trivial glitches that  I really wonder  why one  and a
Rainer> half years later I should be the first one to stumble upon them?

This patch is corrupt and makes no sense, but it does match some of
the problems I run into a points.  

Using 8.2.0b, if I start up VM with my basic autoloads setup, I can't
compose a new email without doing 'r' to reply to an existing email,
then killing that buffer.  Then I can to 'm' to compose an email.

So your patch made me interested to fix my vm-reply.el, but I don't
see that hook or any of those matching lines in the code.  


reply via email to

[Prev in Thread] Current Thread [Next in Thread]