VM

vm-pcrisis not working for vm-compose-mail

Bug #906885 reported by Uday Reddy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Committed
Medium
Uday Reddy

Bug Description

Trying to do `vm-imap-submit-bug-report' resulted in the following error:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("vmrocks" nil)
  vmpc-folder-account-match("vmrocks")
  (and (vmpc-none-true-yet) (vmpc-folder-account-match "vmrocks"))
  (progn (and (vmpc-none-true-yet) (vmpc-folder-account-match "vmrocks")))
  eval((progn (and (vmpc-none-true-yet) (vmpc-folder-account-match "vmrocks"))))
  #[(c) ... [c vmpc-true-conditions eval progn] 3]((in-vmrocks (and (vmpc-none-true-yet) (vmpc-folder-account-match "vmrocks"))))
  mapc(#[(c) ... [c vmpc-true-conditions eval progn] 3] ((to-work-new (vmpc-header-match "To\\|Cc" ...)) (to-work-old (vmpc-header-match "To\\|Cc" ...)) (to-home (vmpc-header-match "To\\|Cc" ...)) (to-vmrocks (vmpc-header-match "To\\|Cc" ...)) (to-launchpad (vmpc-header-match "To\\|Cc" ...)) (to-hotmail (vmpc-header-match "To\\|Cc" ...)) (to-emacs-lists (vmpc-header-match "To\\|Cc" "@.*gnu\\.org")) (to-newsgroups (vmpc-header-match "Newsgroups" "\\(gnu\\|gmane\\).emacs")) (in-vmrocks (and ... ...)) (in-blueyonder (and ... ...))))
  vmpc-build-true-conditions-list()
  vm-compose-mail()
  reporter-compose-outgoing()
  reporter-submit-bug-report("<email address hidden>" "VM 8.2.0a" ...)
  vm-submit-bug-report(nil (#[nil ... [vm-kept-imap-buffers buf bufs nil "\n\n" "IMAP Trace buffers - most recent first\n\n" "----" format "%s" "----------\n" buffer-string "--------------------------------------------------\n"] 4]))
  vm-imap-submit-bug-report()
  call-interactively(vm-imap-submit-bug-report t nil)
  execute-extended-command(nil)
  call-interactively(execute-extended-command nil nil)

Related branches

Uday Reddy (reddyuday)
tags: added: 8.1 compose
removed: add-ons
Revision history for this message
Uday Reddy (reddyuday) wrote :

The problem is that all the VM variables have been sanitized for the sake of the reporter. We should some other mail user agent to send the bug report.

Changed in vm:
status: Triaged → Fix Committed
Revision history for this message
Uday Reddy (reddyuday) wrote :

Changed to message-user-agent (the default in Gnu Emacs). There will be no VM-related functions available here. This could be a problem for some people. Wait and see.

Fix committed in rev. 835.1.458 of the 8.2.x branch.

Changed in vm:
status: Fix Committed → Fix Released
Revision history for this message
Uday Reddy (reddyuday) wrote :

Rob Marshall reports (2012-01-16):

I'm not sure if this is due to the gradual moving over to message mode
and hence a temporary inconsistency or a bug:

If I kill a vm email I get asked if I want to save the message in the
postponed folder (also bound to C-c C-d)
If I kill a vm bug report submission this question doesn't get asked
(you instead get asked if you want to kill a modified buffer) - however
the same C-c C-d binding also maps to something similar - but if you save the
message there it (afaict) isn't visible to vm - I can see it when I run
gnus - as a draft

I lost a bug report earlier today when I thought I'd postpone sending it
and carelessly typed y thinking the question was 'save in postponed'
rather than do you really want to kill this buffer (fortunately the bug
turned out not to be one - that was the reason for the postponment ;-))

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

The problem still persists for vm-imap-submit-bug-report. When it tries to find the session buffers etc., it can't get hold of the account name (lost in the sanitization process).

Changed in vm:
status: Fix Released → In Progress
milestone: 8.2.0b → 8.3.1a
milestone: 8.3.1a → 8.2.1a
Revision history for this message
Uday Reddy (reddyuday) wrote :

Fix committed rev. 1511.

Changed in vm:
status: In Progress → Fix Committed
Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.2.1a → 8.2.90a
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.