<<< Date Index >>>     <<< Thread Index >>>

Re: Subject üî



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, September 18 at 11:55 PM, quoth Alain Bench:
> On Thursday, September 6, 2007 at 16:30:42 -0600, Kyle Wheeler wrote:
>> I had already de-selected "Wide Glyphs count as two columns"
>
>    I wonder what does this option?

 From what I can tell, it allows some characters to take up two 
columns. For example, an em-dash (—) is hard to tell from an en-dash 
(–) or even a hyphen (-) without an actual change in width. This makes 
more sense when using a non-monospaced font (as em-dashes are 
naturally the same width as an m, which are the same width as 
everything else in such fonts). It becomes an issue when mutt does 
something that calls up a symbol from outside the monospaced font, 
such as the horizontal line character used to draw the threading 
arrows. This has a natural width that is slightly wider than all the 
other characters, and so when that option is enabled, the horizontal 
line glyph occupies two columns (it’s centered in the two-column 
area).

At least, I *think* that’s how this works, based on how it seems to 
behave.

Thanks as always, Alain.

~Kyle
- -- 
America will never be destroyed from the outside. If we falter and 
lose our freedoms, it will be because we destroyed ourselves.
                                                     -- Abraham Lincoln
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iD8DBQFG8E94BkIOoMqOI14RAqS9AKD1V/OKFfU5n9cQo3Qh/rxkJFRB4ACeKEBU
Dl8YBjxOKe1tlEMvF9Fp9n0=
=W5Eo
-----END PGP SIGNATURE-----