Re: Subject üî
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday, September 6 at 07:17 PM, quoth Alain Bench:
>> The thread arrows are drawn correctly except that they have spaces
>> between them, like a dashed line. I'll maybe mess with nsterm later.
>
> So that's not a TERM problem: I've already seen screen copies of
> Terminal.app with such small interruptions in lines, especially vertical
> ones. Could it be a font, or font size related problem?
For what it's worth, this problem is relatively easy to fix in the
horizontal case. In your Terminal Settings (select "Window Inspector"
from the Terminal menu), in the Display section, de-select both "Wide
Glyphs..." options.
I had already de-selected "Wide Glyphs count as two columns", but
"Wide Glyphs for Japanese/Chinese/etc." fixed the horizontal
line-breaks for my threading arrows.
If anyone knows a fix for the vertical line breaks, I'd love to know.
> Mutt muttrc tip to send mails in best adapted first necessary and
> sufficient
> charset (version for Western Latin-1/Latin-9/CP-850/CP-1252 terminal users):
> set send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:utf-8"
Oh? Hrm. I had people jumping all over me for my use of windows-1252
(just because I wanted curly-quotes, like this: can’t have ‘em).
That's why my mutt-users posts are (almost) always in non-MIME
us-ascii now. For sending emails with such characters in them (as I do
a *lot*) is it really better to send them encoded as windows-1252 than
as utf-8?
~Kyle
- --
No one will ever win the battle of the sexes; there's too much
fraternizing with the enemy.
-- Henry Kissinger
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFG4H+SBkIOoMqOI14RAnEeAJwNYy+oHTWHAxeAXSU1oPTjkKOxPACg+VBq
TR2ZXeT8MapkJ7ctKFK+hBM=
=qCRJ
-----END PGP SIGNATURE-----