On Sat, Aug 26, 2006 at 11:47:47AM +0200, Alain Bench wrote: > > 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".
That would work for me. Specially if it could do a fall-back utf-8 to latin1, but always having it in utf-8 works for me too. > 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. The proper way would be to set it as forwarded, since it's not actually solved. > > 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. Basicly, I want to store files in UTF-8. I also want to be able to edit files that are stored in UTF-8. And I want to do that regardless of what the terminal is set up to. I don't want to use iconv on a file to convert it from/to utf-8, I want my editor to do that. And I've set up vim to do what I want. It's just that when mutt and vim interact, they don't agree on the character encoding. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
