070812 Benno Schulenberg wrote:
> You will have to use a UTF-8 locale
> if you want mutt/gvim to be able to handle anything beyond ASCII.
> When using a UTF-8 locale, mutt correctly determines
> whether the produced message fits in us-ascii, iso-8859-1 or needs utf-8.
I now have (via a line in .bashrc ):
purslow: ~> locale
LANG=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8
There's no difference in the headers.
It occurs to me that I'm running Mutt via 'konsole -e mutt',
which is restarted automatically by KDE .
I did restart X & thereby KDE & Konsole+Mutt ,
but just possibly that won't use .bashrc : any thoughts ?
> If just setting the better locale doesn't help,
> then also try with an empty .muttrc.
That sounds rather extreme (smile): are there specific lines to comment out ?
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : [EMAIL PROTECTED]
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto
--
[EMAIL PROTECTED] mailing list
