VM

Comment 2 for bug 917772

Revision history for this message
Michael Goldwasser (mgoldwasser) wrote : Re: [Bug 917772] [NEW] vm-save-message will not create new folder

Hello Uday,

Thanks for your help and support for vm.  Attached is (hopefully) the information that you requested via launchpad. In particular, I am including a copy of the backtrace buffer when working in vm-8.1.1 and the backtrace when working in vm-8.2.0b.  I note that with debug, I never even got to the point of entering a filename for the save.

By all means, if this is not quite what you wanted to receive, just let me know what I should be doing and I'll resend.

With regard,
Michael Goldwasser

>________________________________
> From: Uday Reddy <email address hidden>
>To: <email address hidden>
>Sent: Tuesday, January 17, 2012 12:56 PM
>Subject: Re: [Bug 917772] [NEW] vm-save-message will not create new folder
>
>Hi Michael, can you do
>
>  M-x debug-on-entry <RET> vm-read-file-name <RET>
>
>and send me the contents of backtrace buffer you get?  Please email to the
>bug handler or to me at <email address hidden>.  (Don't cut and paste into a
>web page.)
>
>Cheers,
>Uday
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/917772
>
>Title:
>  vm-save-message will not create new folder
>
>Status in VM (View Mail) for Emacs:
>  New
>
>Bug description:
>  Using vm-8.1.1 and earlier,  proper behavior is that when vm-save-
>  message is invoked, if a nonexistent file is indicated in the
>  minibuffer, a file is automatically created and the message saved to
>  it (with or without confirmation, depending on setting of vm-conform-
>  new-folders)
>
>  Using vm-8.2.0b, there seems no way to create a new folder in this
>  way.  If a nonexisting file is indicated in the minibuffer and the
>  return key entered, the minibuffer indicates "[No match]", but no
>  option is given to implicitly/explicitly create such a file.
>
>  To decouple issue of configuration, I am working with the following
>  simple .vm file
>
>  -------------------------------------------------
>  (setq vm-primary-inbox "~/.Mail/INBOX")
>  (setq vm-folder-directory "~/.Mail")
>  ; (setq vm-confirm-new-folders t)                ; bug exists with or without this line
>  -------------------------------------------------
>
>
>  As workaround, I can separately 'touch' the desired file outside of vm, and then I am allowed to save the message, but clearly that is an unnecessary inconvenience.
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/vm/+bug/917772/+subscriptions
>
>
>