A charset question again
Hi All, I've switched my (FreeBSD) system from ISO8859-15 to UTF-8. (jove is less « intelligent » than emacs, ) (but joe is an excellent replacement for jove.) My question concerns html messages encoded in iso8859-1. The subject line displays accented characters alright. But in the body they are all simply replaced by spaces. --- Message: Content-Type: text/html; charset=ISO-8859-1 q:Exit s:Save |:Pipe p:Print ?:Help I 1 no description [text/html, quoted, iso-8859-1, 30K] --- mailcap: text/html; /usr/local/bin/w3m -v -F -T text/html %s --- I've played with Alain Bench's charset-hooks without success. What can I do? -- Harald Weis
Re: A charset question again
Harald Weis wrote: I've switched my (FreeBSD) system from ISO8859-15 to UTF-8. (jove is less « intelligent » than emacs, ) (but joe is an excellent replacement for jove.) My question concerns html messages encoded in iso8859-1. The subject line displays accented characters alright. But in the body they are all simply replaced by spaces. --- Message: Content-Type: text/html; charset=ISO-8859-1 q:Exit s:Save |:Pipe p:Print ?:Help I 1 no description[text/html, quoted, iso-8859-1, 30K] --- mailcap: text/html; /usr/local/bin/w3m -v -F -T text/html %s --- This is really a w3m question rather than a mutt question; anyway it seems w3m is not correctly detecting the terminal encoding. You could try in your mailcap: text/html; /usr/local/bin/w3m -dump -O UTF-8 -F -T text/html %s; copiousoutput -- Chris Burdess
Re: A charset question again
On Wed, Apr 18, 2012 at 12:28:45PM +0100, Chris Burdess wrote: Harald Weis wrote: I've switched my (FreeBSD) system from ISO8859-15 to UTF-8. (jove is less « intelligent » than emacs, ) (but joe is an excellent replacement for jove.) My question concerns html messages encoded in iso8859-1. The subject line displays accented characters alright. But in the body they are all simply replaced by spaces. --- Message: Content-Type: text/html; charset=ISO-8859-1 q:Exit s:Save |:Pipe p:Print ?:Help I 1 no description [text/html, quoted, iso-8859-1, 30K] --- mailcap: text/html; /usr/local/bin/w3m -v -F -T text/html %s --- This is really a w3m question rather than a mutt question; anyway it seems w3m is not correctly detecting the terminal encoding. There is no problem with w3m elsewhere. You could try in your mailcap: text/html; /usr/local/bin/w3m -dump -O UTF-8 -F -T text/html %s; copiousoutput Trial done. No change whatsoever with respect to the accented characters. It seems as if mutt hands over ASCII text to w3m, with spaces instead of the accented characters. What else can I do ? -- Harald
header_cache compiled and enabled, but no caching
I'm having trouble heaでer cahcing from my work IMAP server. I have compiled Mutt 1.5.21 using '--enable-hcache', and mutt -v shows it is indeed enabled: mutt -v Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 3.2.0-2-amd64 (x86_64) ncurses: ncurses 5.9.20110404 (compiled with 5.9) libidn: 1.23 (compiled with 1.23) hcache backend: tokyocabinet 1.4.37 Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/local/share/mutt SYSCONFDIR=/usr/local/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. My header_cache is also defined in my muttrc: set header_cache=/home/epatton/.mutt_cache/ (File permissions set to 666.) Despite this, the mail headers get read from scratch upon each Mutt startup. Not sure what else I'm missing here. Everything else in Mutt is fine. ~ Eric.
New mail indicator
I have a very simple question but cannot find the answer anywhere.
I have mutt setup with offlineimap using maildir format. When I press
`y` to change to one of my mailbox, and there is some unread mail in
the current folder, if I change to another folder, the new mail
indicator ('N' character) disappear. How can I keep that 'N'? I
always have a hard time searching for unread mails.
--
PHẠM Văn Điệp
h : http://favadi.com
e : i...@favadi.com
m : +84 984 339 841
_
ASCII ribbon campaign ( )
- against HTML email X
vCards / \
Re: A charset question again
Harald Weis wrote:
You could try in your mailcap:
text/html; /usr/local/bin/w3m -dump -O UTF-8 -F -T text/html %s;
copiousoutput
Trial done. No change whatsoever with respect to the accented characters.
It seems as if mutt hands over ASCII text to w3m, with spaces instead of the
accented characters.
What else can I do ?
Sorry, my bad. It's the input encoding that's the problem, not the output
encoding.
This works (tested just now) for me:
text/html; w3m -dump -I %{charset} %s; copiousoutput
--
Chris Burdess
Re: header_cache compiled and enabled, but no caching
set header_cache=/home/epatton/.mutt_cache/ (File permissions set to 666.) Shouldn't that be 777? -- --|-- | Patrice Levesque http://ptaff.ca/ mutt.wa...@ptaff.ca | --|-- -- signature.asc Description: Digital signature
Re: header_cache compiled and enabled, but no caching
On Wed, Apr 18, 2012, Patrice Levesque wrote: set header_cache=/home/epatton/.mutt_cache/ (File permissions set to 666.) Shouldn't that be 777? I just tried chmoding my .mutt_cache to 777, and exiting and re-starting Mutt to no avail - headers are still being downloaded anew. The size of ~/.mutt_cache remains 0 as well. ~ Eric
Re: New mail indicator
On Wed, Apr 18, 2012 at 10:51:02PM +0700, Diep Pham Van wrote:
I have mutt setup with offlineimap using maildir format. When I press
`y` to change to one of my mailbox, and there is some unread mail in
the current folder, if I change to another folder, the new mail
indicator ('N' character) disappear. How can I keep that 'N'? I
always have a hard time searching for unread mails.
Do they show up with an 'O' after you re-enter the folder?
Have you tried
unset mark_old ?
w
Re: A charset question again
On Wed, Apr 18, 2012 at 05:00:17PM +0100, Chris Burdess wrote:
Harald Weis wrote:
You could try in your mailcap:
text/html; /usr/local/bin/w3m -dump -O UTF-8 -F -T text/html %s;
copiousoutput
Trial done. No change whatsoever with respect to the accented characters.
It seems as if mutt hands over ASCII text to w3m, with spaces instead of the
accented characters.
What else can I do ?
Sorry, my bad. It's the input encoding that's the problem, not the output
encoding.
This works (tested just now) for me:
text/html; w3m -dump -I %{charset} %s; copiousoutput
Great, that works indeed. :)
Thank you very much, Chris.
--
Harald
Re: header_cache compiled and enabled, but no caching
On Wed, Apr 18, 2012 at 12:40:09PM -0300, Eric Patton wrote: I have compiled Mutt 1.5.21 using '--enable-hcache', and mutt -v shows it is indeed enabled: [snip] My header_cache is also defined in my muttrc: set header_cache=/home/epatton/.mutt_cache/ (File permissions set to 666.) Despite this, the mail headers get read from scratch upon each Mutt startup. Are you sure? How do you know? You didn't describe the symptoms you're seeing... it's possible that whatever you're seeing (I assume it's slowness opening mailboxes) is caused by something else. Did you try running with debugging enabled, and did you review the debug log? Is there anything in your cache directory? Did you try removing the cache and restarting Mutt? -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpXfbirtYh9p.pgp Description: PGP signature
Re: header_cache compiled and enabled, but no caching
On 18Apr2012 12:28, Patrice Levesque mutt.wa...@ptaff.ca wrote: | set header_cache=/home/epatton/.mutt_cache/ | (File permissions set to 666.) | | Shouldn't that be 777? Whatever for? It only needs to be writable by the user, being a directory, 700 or 750 o 755 perhaps. Admittedly 666 (or 600 etc - anything not including the 'x' (search) bit) will break things, as a directory needs search permission for you to access files within it. Cheers, -- Cameron Simpson c...@zip.com.au DoD#743 http://www.cskk.ezoshosting.com/cs/ No real plot, some good special effects, but not enough to save this very forgettable film. SN: Windows 95. - Phil Herring rev...@uow.edu.au on _Mission Impossible_
Re: header_cache compiled and enabled, but no caching
On 18Apr2012 13:40, Eric Patton epat...@nrcan.gc.ca wrote: | On Wed, Apr 18, 2012, Patrice Levesque wrote: | set header_cache=/home/epatton/.mutt_cache/ | (File permissions set to 666.) | | Shouldn't that be 777? | | | I just tried chmoding my .mutt_cache to 777, and exiting and re-starting | Mutt to no avail - headers are still being downloaded anew. Well, they will the first time if the cache is empty. | The size of | ~/.mutt_cache remains 0 as well. Very suspect. You _did_ make a directory for the cache, and not a file? mkdir ~/.mutt_cache What does: ls -ld ~/.mutt_cache ls -la ~/.mutt_cache show? -- Cameron Simpson c...@zip.com.au DoD#743 http://www.cskk.ezoshosting.com/cs/ No, Sir. I don't think its safe to look at the speedometer when I'm going that fast. - Tom Coradeschi tc...@pica.army.mil
