vm team mailing list archive

[Göran Uddeborg <goeran@xxxxxxxxxxx>]

Public bug reported:

Since switching do vm 8.1.0 beta I've occasionally experienced failures
when trying to forward a message.  Instead of getting a composition
buffer with the message to be forwarded attached, I get a frame split
into two windows.  I haven't figured out exactly what triggers it, but I
attach a sample (stripped down) message that illustrates the problem.

To reproduce:
- Move away any .vm file
- Start "emacs -q"
- Do M-x vm-visit-folder
- Select the folder attached to this report
- Hit "z" to forward the message

Now I wind up with two windows in the new frame.  The upper is the
composition buffer with the proper subject line, but no message
attached.  The lower contains the header of the message to be forwarded.

I assume this is a problem in vm itself.  But just in case it matters, I
experience this on a Fedora 12 system with

emacs-23.1-13.fc12.x86_64
emacs-vm-8.1.0-0.1.beta.fc12.x86_64

** Affects: vm
     Importance: Undecided
         Status: New

-- 
Forwarding breaks on certain messages, 8.1.0 beta
https://bugs.launchpad.net/bugs/508493
You received this bug notification because you are a member of VM
development team, which is the registrant for VM.

Status in VM (View Mail) for Emacs: New

Bug description:
Since switching do vm 8.1.0 beta I've occasionally experienced failures when trying to forward a message.  Instead of getting a composition buffer with the message to be forwarded attached, I get a frame split into two windows.  I haven't figured out exactly what triggers it, but I attach a sample (stripped down) message that illustrates the problem.

To reproduce:
- Move away any .vm file
- Start "emacs -q"
- Do M-x vm-visit-folder
- Select the folder attached to this report
- Hit "z" to forward the message

Now I wind up with two windows in the new frame.  The upper is the composition buffer with the proper subject line, but no message attached.  The lower contains the header of the message to be forwarded.

I assume this is a problem in vm itself.  But just in case it matters, I experience this on a Fedora 12 system with

emacs-23.1-13.fc12.x86_64
emacs-vm-8.1.0-0.1.beta.fc12.x86_64