On Wednesday, October 06, 2010 a las 11:07:02AM -0400, Nathan Stratton Treadway
wrote:
On Wed, Oct 06, 2010 at 15:48:20 +0200, Matthias Apitz wrote:
What combination of terminal and editor should be used now? When I'm
receiving an ISO-8859-1 message with, for example, the Spanish char á
On Thu, Oct 07, 2010 at 15:03:57 +0200, Matthias Apitz wrote:
On Wednesday, October 06, 2010 a las 11:07:02AM -0400, Nathan Stratton
Treadway wrote:
In each of your two vim sessions, what does
:set encoding fileencoding fileencodings termencoding
show?
[...]
Xterm (ISO-8859-1) and
El día Tuesday, October 05, 2010 a las 02:25:03PM -0500, Kyle Wheeler escribió:
On Tuesday, October 5 at 08:58 PM, quoth Matthias Apitz:
In the output of mutt -v it says (among other stuff):
-HAVE_ICONV
-ICONV_NONTRANS
Ahhh, there you go.
The ./configure was indeed done without
El día Wednesday, October 06, 2010 a las 09:55:08AM +0200, Matthias Apitz
escribió:
The ./configure was indeed done without pointing it to the location of
libiconv and so iconv support was mapped out. I corrected this now, but:
when I run ./configure as:
# ./configure --enable-imap
It seems I have opened now the Pandora's box :-)
Kyle,
What combination of terminal and editor should be used now? When I'm
receiving an ISO-8859-1 message with, for example, the Spanish char á
(0xe1 in ISO) and I do a reply then:
with xterm (ISO-8859-1) and 'vim' the á is correctly presented
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, October 6 at 03:48 PM, quoth Matthias Apitz:
It seems I have opened now the Pandora's box :-)
Indeed! But at some point, it'll Just Work (tm).
What combination of terminal and editor should be used now? When I'm
receiving an
El día Wednesday, October 06, 2010 a las 09:17:48AM -0500, Kyle Wheeler
escribió:
On Wednesday, October 6 at 03:48 PM, quoth Matthias Apitz:
It seems I have opened now the Pandora's box :-)
Indeed! But at some point, it'll Just Work (tm).
What combination of terminal and editor should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, October 6 at 04:31 PM, quoth Matthias Apitz:
It's because vim isn't *told* what character set the input file
will be; it has to guess. Mutt is handing it a UTF-8 file (because
mutt converts mail messages into whatever the local
On Wed, Oct 06, 2010 at 09:52:22AM -0500, Kyle Wheeler wrote:
On Wednesday, October 6 at 04:31 PM, quoth Matthias Apitz:
It is converted *before* it is stored into the temp file for 'vim'; I've
checked this with truss(1) what mutt hands over to vim (see the
marked bytes):
[...]
On Wed, Oct 06, 2010 at 15:48:20 +0200, Matthias Apitz wrote:
What combination of terminal and editor should be used now? When I'm
receiving an ISO-8859-1 message with, for example, the Spanish char á
(0xe1 in ISO) and I do a reply then:
with xterm (ISO-8859-1) and 'vim' the á is correctly
0n Wed, Oct 06, 2010 at 10:00:27AM -0500, Nicolas Williams wrote:
It is, since Matthias must be using Solaris (given the reference to
truss(1)),
#uname -s which truss
FreeBSD
/usr/bin/truss
:P
-Alex
IMPORTANT: This email remains the property of the Department of Defence and
El día Wednesday, October 06, 2010 a las 09:52:22AM -0500, Kyle Wheeler
escribió:
Well, of course it is. When mutt reads an email message, it reads it
into it's own local memory, transforms it into a form that is
convenient to think about (in this case, utf-8), and uses that to
display to
On Wed, Oct 06, 2010 at 11:07:28PM +0800, Wilkinson, Alex wrote:
0n Wed, Oct 06, 2010 at 10:00:27AM -0500, Nicolas Williams wrote:
It is, since Matthias must be using Solaris (given the reference to
truss(1)),
#uname -s which truss
FreeBSD
/usr/bin/truss
:P
Ah... OK,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, October 6 at 05:07 PM, quoth Matthias Apitz:
You are right, but only half way :-)
In parts it is written in ISO-8859-1
I found the reason. From .muttrc the $attribution was inserted as
El día %d, %n escribió:\n
Ahhh, I see.
On Wed, Oct 06, 2010 at 10:00:27AM -0500, Nicolas Williams wrote:
It is, since Matthias must be using Solaris (given the reference to
truss(1)), and on Solaris es_ES.UTF-8 is very much a valid locale name.
Of course, that locale might not be _installed_, so the locale -a check
is still a good
El día Monday, October 04, 2010 a las 11:06:22PM -0500, Kyle Wheeler escribió:
I've been using mutt as a UTF-8 enabled program for... gosh,
probably four years now. So, it works, and it works well. Here are
some things to consider, though:
1. As has been said, mutt uses the smallest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tuesday, October 5 at 11:58 AM, quoth Matthias Apitz:
Error in /home/guru/.muttrc, line 70: Invalid value for option
send_charset: us-ascii:iso-8859-1:utf-8
I double checked this against the man page and even cutpaste the value
from there...
El día Tuesday, October 05, 2010 a las 10:19:29AM -0500, Kyle Wheeler escribió:
On Tuesday, October 5 at 11:58 AM, quoth Matthias Apitz:
Error in /home/guru/.muttrc, line 70: Invalid value for option
send_charset: us-ascii:iso-8859-1:utf-8
I double checked this against the man page and
On Mon, Oct 04, 2010 at 11:35:03AM +0200, Matthias Apitz wrote:
At the moment I still have set the xterm for mutt to ISO-8859-1, i.e.
receiving and sending messages in ISO. More and more I receive email now
in UTF-8 and to read them I open another terminal 'urxvt' with the LANG
set to
On 04.10.10,11:35, Matthias Apitz wrote:
Hello,
At the moment I still have set the xterm for mutt to ISO-8859-1, i.e.
receiving and sending messages in ISO. More and more I receive email now
in UTF-8 and to read them I open another terminal 'urxvt' with the LANG
set to es_ES.UTF-8 to read
On 04.10.10 11:35:03, Matthias Apitz wrote:
At the moment I still have set the xterm for mutt to ISO-8859-1, i.e.
receiving and sending messages in ISO. More and more I receive email now
in UTF-8 and to read them I open another terminal 'urxvt' with the LANG
set to es_ES.UTF-8 to read such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Monday, October 4 at 11:25 AM, quoth Athanasius:
I'm unsure if I should completely switch to UTF-8 already, maybe
this would cause big disaster in the receiving sites, mailing lists
etc. What is the opinion about of other mutt users and
22 matches
Mail list logo