package mutt
severity 384642 wishlist
close 384642
thanks
Hello Kurt, and thanks for the report.
On Friday, August 25, 2006 at 19:09:32 +0200, Kurt Roeckx wrote:
> I'm using a latin1 terminal, but I've set up vim to use utf-8 files by
> default, but fall back to latin1. Vim also shows latin1 on the screen.
> But I can't seem to get mutt and vim to agree on the charset for the
> file being used.
That's not possible today. You need to setup the $editor to read and
write files exclusively and dumbly in the current locale charset, when
it is called by Mutt.
What you ask would make sense in some situations (like Mutt in a L1
term calling gvim in UTF, and such), and is already on the upstream Mutt
wishlist/1317: "Add config var edit_charset".
I close this Debian bug as duplicate (in upstream BTS Gnats, we
don't merge but close dupes), and will add you to the interested parties
of /1317.
> 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.
Keep the later value. But $file_charset acts on text files you
<attach-file> from the compose menu, not on the text you write.
> 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.
You're right. Why do you want another charset? Knowing your exact
goal, we could perhaps suggest other means. Probably a topic more for
mutt-users mailing list or comp.mail.mutt than for a BTS, though.
Bye! Alain.
--
Everything about locales on Sven Mascheck's excellent site at new
location <URL:http://www.in-ulm.de/~mascheck/locale/>. The little tester
utility is at <URL:http://www.in-ulm.de/~mascheck/locale/checklocale.c>.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
