vm-reply-include-xxxx broken when font is in vm-mime-default-face-charsets
Bug #611393 reported by
blueman
This bug report is a duplicate of:
Bug #708124: vm-included-mime-types-list seems redundant.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VM |
Triaged
|
Low
|
Uday Reddy |
Bug Description
The vm-reply-
This was working properly as recently as 8.0.12...
Not sure what new change broke this...
In the past this function used to work whether or not the font was in
the vm-mime-
Note the standard vm function vm-reply-
broken...
I am using vm 8.1.1.
Changed in vm: | |
status: | New → Incomplete |
importance: | Undecided → Medium |
milestone: | none → 8.1.93a |
assignee: | nobody → Uday Reddy (reddyuday) |
milestone: | 8.1.93a → 8.1.2 |
tags: | added: reply |
Changed in vm: | |
status: | Incomplete → Confirmed |
importance: | Medium → Low |
Changed in vm: | |
milestone: | 8.1.2 → 8.2.0b |
status: | Confirmed → Triaged |
To post a comment you must log in.
Welcome to Launchpad!
It is working fine for me.
By non-MIME message do you mean that it doesn't have a MIME-version
header? What are the MIME headers exactly?
There are three versions of include in VM right now. Please place a message- presentation, message- mime and vm-yank- message- text, to see which one is message- mime is the preferred version and it
debug-on-entry on all of them: vm-yank-
vm-yank-
getting entered. vm-yank-
is selected by the default settings of VM. If you are getting
something different, let me know what settings you are using.
Cheers,
Uday