On Friday, August 25 at 07:09 PM, quoth Kurt Roeckx:
So, I was reading the documentation, and it seems that the only thing that I should consider changing seems to be file_charset. I've tried setting that to various things like just "utf-8", or "utf-8:iso-8859-1", but it doesn't seem to be changing anything.
Mutt degrades the charset to the weakest one necessary. In other words, if the characters that you use in your file are all valid iso-8859-1 characters, then mutt will treat the file as iso-8859-1.
This is generally considered a good thing because more people can read iso-8859-1 files than can read utf-8 files, and there’s no reason to call it utf-8 if there’s a more common charset that correctly describes the file’s contents.
It seems that mutt always considers the encoding of the filename to be the same as for the terminal, and that's not really what I want.
Wait, you’re trying to make the *filename* be encoded in utf-8?
Forcing the charset to utf-8 to seems to be working, but then I can't properly read mails in mutt.
Why can’t you properly read mails in mutt? ~Kyle -- Men at some time are masters of their fates:The fault, dear Brutus, is not in our stars,
But in ourselves, that we are underlings.
-- Shakespeare, in Julius Caesar
pgpoCJ6apRQi9.pgp
Description: PGP signature
