VM

vm-save-message will not create new folder

Bug #917772 reported by Michael Goldwasser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Committed
Low
Uday Reddy

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.

Related branches

Revision history for this message
Uday Reddy (reddyuday) wrote : 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

Revision history for this message
Michael Goldwasser (mgoldwasser) wrote :

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
>
>
>

Revision history for this message
Uday Reddy (reddyuday) wrote :

Thanks, Michael. Let us see if this patch gets you out of the problem.

I realized that asking for confirmation during completion forced it to fail if there was no match. I removed the confirmation request in two cases but retained it in the other. I can't now remember why I retained it in the other case. But we will get rid of it altogether.

Changed in vm:
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Uday Reddy (reddyuday)
milestone: none → 8.2.90a
Revision history for this message
Michael Goldwasser (mgoldwasser) wrote :

Uday, unfortunately, this patch does not seem to change the behavior for me. Of course, unless I'm missing something, that patch did not make any non-trivial changes to vm-save.el; it simply changed some whitespace. In particular, the confirm is still retained in the third case.

Revision history for this message
Michael Goldwasser (mgoldwasser) wrote :

As followup, if I do comment out the third case of confirm, this resolves the problem I reported
(sorry for not trying that obvious step before my previous post).

Revision history for this message
Uday Reddy (reddyuday) wrote : [Bug 917772] Re: vm-save-message will not create new folder

Michael Goldwasser writes:

> Uday, unfortunately, this patch does not seem to change the behavior for
> me. Of course, unless I'm missing something, that patch did not make
> any non-trivial changes to vm-save.el; it simply changed some
> whitespace. In particular, the confirm is still retained in the third
> case.

You are right. I think I need to take a pause for a few days, because I am
making silly mistakes....

Cheers,
Uday

Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.2.90a → 8.2.89a
Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.2.89a → 8.2.0b1
no longer affects: vm/8.2.x
Revision history for this message
Uday Reddy (reddyuday) wrote :

It looks like a full fix was committed in rev. 1345. We will revisit it again if it doesn't cure the problem.

Changed in vm:
status: In Progress → Fix Committed
Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.2.1a → 8.2.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.