I emerged urlview recently: [miniscd:/home/aarenson] bash> genlop urlview * net-misc/urlview Merged at Tue Nov 11 22:38:34 2003 (urlview-0.9) Merged at Fri Feb 20 22:27:08 2004 (urlview-0.9) And today noticed that urlview was inserting extra characters into URLs. For instance, the URL: http://app2.topiksolutions.com/jump.ts?t=167&m=2292&p=900894&a=296 became: http://app2.topiksolutions.com/jump.ts?t=3D167&m=3D2292&p=3D900894&a=3D296 This appears to occur for all equal signs in the URL. Oddly, I couldn't reproduce the problem in a test email I sent myself, but I've got two emails in my inbox (from the same parent organization) that are exhibiting this behavior). Reproducible: Couldn't Reproduce Steps to Reproduce: 1. 2. 3.
Created attachment 26335 [details] Email exhibiting strange behavior when used w/ urlview
No clue over here, also i can't reproduce it, anyone else?
Andrew, what's your default charset? (If that's not the right word, my apologies). In other words, could it be a unicode/ascii type issue?
Created attachment 27399 [details] Email exhibiting strange behavior when used w/ urlview My apologies, the email I attached earlier doesn't exhibit this behavior. This email, though, is the one from which I drew my example in the original bug report.
Not exactly sure what to look for to determine my default charset. I have noticed that the failing email includes: Content-Type: text/plain; charset=us-ascii And I've been told that the default character set for Linux is ISO-8859-1. I've noticed nothing in my .muttrc that sets a character set
sorry, but i don't know what i have to do with this?
If you receive a mail that has Content-Disposition: quoted-printable rather than Content-Disposition: inline, does the same thing happen?
Also, I have two other things for you to try. First of all, try bouncing the email to yourself, only changing the Content-Disposition header to quoted-printable. If you "set pipe_decode" in your muttrc does it still happen?
Andrew, any response to Tom's questions?
Sorry for the delay in responding. I was unable to find Content-Disposition in the headers of my example email w/ the problem. BUT, I'm happy to report that "set pipe_decode" appears to have fixed my problem! A quick google search, after finding that pipe_decode worked for me, lead me to add these .muttrc entries: #get all of the URL's from a message and view with browser macro index \Cb ":set pipe_decode\n|urlview\n:unset pipe_decode\n" macro pager \Cb ":set pipe_decode\n|urlview\n:unset pipe_decode\n" macro attach \Cb ":set pipe_decode\n|urlview\n:unset pipe_decode\n" And, for future reference of anyone wondering what pipe_decode does: 6.3.153. pipe_decode Type: boolean Default: no Used in connection with the pipe-message command. When unset, Mutt will pipe the messages without any preprocessing. When set, Mutt will weed headers and will attempt to PGP/MIME decode the messages first.
I've added an einfo to urlview to notify users wishing to use this program with mutt about this problem, and how to remedy it. Thanks for reporting, Andrew :)
