Re: quoting urls in replies
- To: mutt-users@xxxxxxxx
- Subject: Re: quoting urls in replies
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Tue, 10 Feb 2009 08:55:18 -0600
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=cROpxzBGeV4P/DMIqUdurr9Usag=; b=UwLx d41PubzNpkyfAtCIw2mF8KD3Y3A35OMDB+wzBvUNpvGrYKu240xSXtbNxznCAbOT 9hfEtuS2nYeKgkYro/wZSGvXAbndw1d1ZJ7zFfhafBNObd1tfDh88ncd72fL1+Jo fEkuN2IgG2Wo7UN1N0Rb2V82R9i2p5p0TPL/a7o=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=IrUku6CgehQYH4BNCYOIBmHNTRjE7qCKZZNsPmz5bL60ahezRqLVRF1Vh8OfeJrLRqhVEE+VWjKzigwS9qur44r0DrR9sMsMP1kIa1ntANcFX5GB9RNbJyQJnzboyvh3/fGzeLoKuh9lCIRr0x7kQ3mxZwKPCy2EEYULm8ZcUMg=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20090210110536.GI26506@xxxxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20090210110536.GI26506@xxxxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.19 (2009-01-27)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, February 10 at 12:05 PM, quoth Rejo Zenger:
> Of course, mutt is doing fine. Just recently, I changed the locale
> to be used by mutt (I changed the charset setting)
Changing the $charset setting manually is *usually* a bad idea; mutt
is very good at figuring out what the correct value for that setting
should be. If you're having a problem, something else will probably be
more effective.
Keep in mind that $charset tells mutt what characters it's allowed to
display. This has nothing to do with the email, and has everything to
do with your terminal. Usually this is controlled via the $LANG
environment variable (or the $LC_* variables, if you want more
precision). The reason for this is that many components of your
system, in addition to mutt, need to know this information (for
example, your termcap library needs to know).
If you truly do have a terminal that is capable of displaying UTF-8
output (and has that option turned on), then you should probably set
your LANG to be something ending in ".utf8". For example, I use a LANG
setting of "en_US.UTF-8". Find out what your options are by running
the program `locale -a`.
> because the threads were incorrectly rendered in the message
> listing.
This sounds more likely to be a problem that would be solved by using
the $assumed_charset setting (which is intended to help address the
rather common problem of incorrectly encoded email).
> Possibly relevant settings in my mutt configuration:
>
> set charset = utf-8
Do not set this yourself (unless you really REALLY know what you're
doing).
> set escape = ~
> set editor = 'vim -c "set tw=72 fo+=aw smartindent" +2'
> set indent_string = ">"
> set use_8bitmime = no
The rest of these are pretty typical.
If you normally correspond with people who speak English or another
western-European language, you probably want to start by adding this
line to your muttrc:
set assumed_charset = "cp1252"
If you want to be more comprehensive, add these as well:
charset-hook ^unknown-8bit$ windows-1252
charset-hook ^x-user-defined$ windows-1252
charset-hook ^iso-8859-1$ windows-1252
charset-hook ^us-ascii$ windows-1252
charset-hook ^none$ windows-1252
charset-hook ^iso-8859-8-u$ iso-8859-8
charset-hook ^gb2312$ gb18030
~Kyle
- --
I prefer to be called "EVIL GENIUS!"
-- Jumba, from "Lilo & Stitch"
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkmRlVUACgkQBkIOoMqOI16jcwCg+JlovV/+3a2GJatcnYWviqiq
lXwAoN4jjx9AHKPUariHopxagQNQW0oW
=pC2B
-----END PGP SIGNATURE-----