Re: Subject üî

2007-09-19 Thread Christian Ebert
* Kyle Wheeler on Tuesday, September 18, 2007 at 17:21:44 -0500 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

Re: Subject üî

2007-09-18 Thread Alain Bench
On Thursday, September 6, 2007 at 15:34:16 -0700, Breen Mullins wrote: superficially it looks like it was in the linker? | #0 0x93c10d7c in dyld_stub_unctrl () Or like some Ncurses thinggy bellow waddnstr(), and specific to the linker? I don't know. This should probably be reported to

Re: Subject üî

2007-09-18 Thread 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? For sending emails with such [curly quotes] characters in them (as I do a *lot*) is it really better to send them encoded as

Re: Subject üî

2007-09-18 Thread Kyle Wheeler
-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

Re: Subject üî

2007-09-18 Thread Breen Mullins
* Alain Bench [EMAIL PROTECTED] [2007-09-18 22:52 +0200]: On Thursday, September 6, 2007 at 15:34:16 -0700, Breen Mullins wrote: superficially it looks like it was in the linker? | #0 0x93c10d7c in dyld_stub_unctrl () Or like some Ncurses thinggy bellow waddnstr(), and specific to the

Re: Subject üî

2007-09-10 Thread dv1445
Thus spake Kyle Wheeler [09/07/07 @ 08.01.34 -0500]: Latin1 it is, until further bizarre things pop up. Plus, xterm under X11 does it right under Latin1, while it is screwy under UTF-8. (uxterm and other things, like the -u8 option and friends, resulted in messed-up colors, including no

Re: Subject üî

2007-09-10 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, September 10 at 03:42 PM, quoth [EMAIL PROTECTED]: I've tried setting it to xterm-16color, 256color, and just color, all with no dice. The messed-up colors have a precedent. When I installed OSX 10.4 with Apple's X11, the colors were

Re: Subject üî

2007-09-10 Thread dv1445
Thus spake Kyle Wheeler [09/10/07 @ 15.13.49 -0500]: On Monday, September 10 at 03:42 PM, quoth [EMAIL PROTECTED]: I've tried setting it to xterm-16color, 256color, and just color, all with no dice. The messed-up colors have a precedent. When I installed OSX 10.4 with Apple's X11, the

Re: Subject üî

2007-09-10 Thread Eyolf Østrem
On 10.09.2007 (17:38), [EMAIL PROTECTED] wrote: Thanks for the link and info. I may play around with it, but I'm hesitant, because xterm's colors are just fine *unless* I either (1) call uxterm, or (2) call the factory xterm from Apple as opposed to the one I built myself. If I tweak

Re: Subject üî

2007-09-10 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, September 10 at 05:38 PM, quoth [EMAIL PROTECTED]: Thanks for the link and info. I may play around with it, but I'm hesitant, because xterm's colors are just fine *unless* I either (1) call uxterm, or (2) call the factory xterm from

Re: Subject üî

2007-09-10 Thread dv1445
Thus spake Kyle Wheeler [09/10/07 @ 18.25.23 -0500]: And of course, you can try them out, and if you don't like the results, change it back to how it is now without a second thought. :) I don't know what it is now, since I do not have an ~/.Xdefaults file. (not in my home dir anyway). Can I

Re: Subject üî

2007-09-10 Thread dv1445
Thus spake Kyle Wheeler [09/10/07 @ 18.25.23 -0500]: And of course, you can try them out, and if you don't like the results, change it back to how it is now without a second thought. :) As a matter of fact, I don't seem to have .Xdefaults *anywhere* on my machine. There is something called

Re: Subject üî

2007-09-10 Thread Gary Johnson
On 2007-09-10, [EMAIL PROTECTED] wrote: Thus spake Kyle Wheeler [09/10/07 @ 18.25.23 -0500]: And of course, you can try them out, and if you don't like the results, change it back to how it is now without a second thought. :) I don't know what it is now, since I do not have an

Re: Subject üî

2007-09-10 Thread Eyolf Østrem
On 10.09.2007 (19:38), [EMAIL PROTECTED] wrote: Thus spake Kyle Wheeler [09/10/07 @ 18.25.23 -0500]: And of course, you can try them out, and if you don't like the results, change it back to how it is now without a second thought. :) As a matter of fact, I don't seem to have .Xdefaults

Re: Subject üî

2007-09-07 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, September 6 at 08:59 PM, quoth [EMAIL PROTECTED]: Latin1 it is, until further bizarre things pop up. Plus, xterm under X11 does it right under Latin1, while it is screwy under UTF-8. (uxterm and other things, like the -u8 option and

Terminfo settings et al. (was: Subject üî)

2007-09-07 Thread Eyolf Østrem
It seems to me that my own problems are related to this thread, so I'll chime in here (with a Was:... change of the subject line). I've found some really useful information, both in the reply to my intial mail a few days back, and in this thread, but my attempts at changing things here and there

Re: Subject üî

2007-09-06 Thread Alain Bench
Hello Kyle, On Tuesday, September 4, 2007 at 23:01:13 -0600, Kyle Wheeler wrote: What makes you say that [UTF-8 on Macs is] less stable? There were several reports of Mutt freezes on MacOS-X in UTF-8 locales, when stepping on various sorts of mails with invalid characters (and now even on

Re: Subject üî

2007-09-06 Thread Alain Bench
On Wednesday, September 5, 2007 at 11:32:03 -0400, [EMAIL PROTECTED] wrote: Thus spake Alain Bench [09/05/07 @ 00.01.21 +0200]: I dropped the replacements, and just kept the uia in subject I'm in console vim composing the reply, and the subject line characters are rendered properly, i.e.,

Re: Subject üî

2007-09-06 Thread Alain Bench
Hi Breen, On Tuesday, September 4, 2007 at 20:09:14 -0700, Breen Mullins wrote: the U+FFDD this morning caused mutt to freeze [...] I got a backtrace this time, if it's helpful. Looks like it's in the library. Which library? Last backtrace I saw of such a MacOS freeze pointed to Ncurses

Re: Subject üî

2007-09-06 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, September 6 at 08:08 PM, quoth Alain Bench: Hello Kyle, Hiya Alain, There were several reports of Mutt freezes on MacOS-X in UTF-8 locales, when stepping on various sorts of mails with invalid characters (and now even on the

Re: Subject üî

2007-09-06 Thread Kyle Wheeler
-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

Re: Subject üî

2007-09-06 Thread Breen Mullins
* Alain Bench [EMAIL PROTECTED] [2007-09-06 19:19 +0200]: Hi Breen, Which library? Last backtrace I saw of such a MacOS freeze pointed to Ncurses waddch_nosync(). But I'd tend to suspect more something in the libc, called by Ncurses. Ugh. I'm not sure I know how to read this -

Re: Subject üî

2007-09-06 Thread dv1445
Thus spake Alain Bench [09/06/07 @ 19.17.56 +0200]: And the ui arrived here cleanly. This may mean the replacements were inserted when you entered the uia. Where? At Mutt's subject prompt? Or in Vim in $edit_headers? Typed, or Pasted? Hmm, I don't know. I didn't paste it in. I'm pretty

Re: Subject üî

2007-09-05 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, September 4 at 11:26 PM, quoth Kyle Wheeler: Speaking of which, any idea how to get it to behave in a more xterm-like fashion? Namely, when I exit a program (such as man or less or mutt), I like that xterm restores the terminal to

Re: Subject üî

2007-09-05 Thread dv1445
Thus spake Alain Bench [09/05/07 @ 00.01.21 +0200]: Exactly. When I said they have to agree, it was about the charset only. However, muttrc doesn't want to set $charset: The default value is automatically derived from the current locale. This automatic link was absent or broken in previous

Re: Subject üî

2007-09-04 Thread Alain Bench
On Monday, September 3, 2007 at 15:22:31 -0400, [EMAIL PROTECTED] wrote: my muttrc, which wants to see set charset=UTF-8 instead of =en_US.UTF-8, while the latter is what $LANG wants to see. Exactly. When I said they have to agree, it was about the charset only. However, muttrc doesn't

Re: Subject üî

2007-09-04 Thread Breen Mullins
* Alain Bench [EMAIL PROTECTED] [2007-09-05 00:01 +0200]: On Monday, September 3, 2007 at 15:22:31 -0400, [EMAIL PROTECTED] wrote: All seems well in body. Subject is []üîå[], meaning uia flanked by 2 U+FFFD replacement characters (in my font they look like empty squares). That seems to be

Re: Subject üî

2007-09-04 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, September 5 at 12:01 AM, quoth Alain Bench: It is however a little less portable, a little more difficult to setup (nothing hairy), and on Macs a little less stable. I haven't had any trouble with it on Macs, and Macs are what I use

Re: Subject üî

2007-09-04 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, September 4 at 11:01 PM, quoth Kyle Wheeler: Those semigraphic chars should work provided that $charset=utf-8 exactly (that's the default value derived from LANG=en_US.UTF-8), that TERM=nsterm-16color, and that you have unchecked