727 reputation
312
bio website
location
age
visits member for 2 years, 7 months
seen 10 hours ago

Aug
26
comment Corrupted gnu-screen session not displaying UTF-8 correctly
@n.m.: sorry, that crucial chunk of information got lost in a cut-and-paste shuffle; I've now fixed the error (see UPDATE)
Aug
26
revised Corrupted gnu-screen session not displaying UTF-8 correctly
added 157 characters in body
Aug
26
revised Corrupted gnu-screen session not displaying UTF-8 correctly
added 1190 characters in body
Aug
26
comment Corrupted gnu-screen session not displaying UTF-8 correctly
...In any case, I will set my locale for future sessions, but is there any way to fix the current "corrupted" gnu-screen session?
Aug
26
comment Corrupted gnu-screen session not displaying UTF-8 correctly
@DravSloan (and @StephaneChazelas) in my current configuration for OS X I'm not setting any locale-related variable. I'm not sure why this is, since my configurations for Linux do set LANG and LC_ALL to en_US.utf8. I do remember having spent a few crazy hours some time ago trying to figure out how to set the locale for OS X Lion, and finding copious amounts of contradictory information... My current OS X configuration, despite not setting the locale, does work normally (i.e. fresh gnu-screen sessions work fine)...
Aug
26
revised Corrupted gnu-screen session not displaying UTF-8 correctly
added 389 characters in body; edited tags
Aug
26
asked Corrupted gnu-screen session not displaying UTF-8 correctly
Aug
22
accepted strange “bad file descriptor” error
Aug
21
comment strange “bad file descriptor” error
Thanks, I've added information to my post that addresses your questions.
Aug
21
revised strange “bad file descriptor” error
added 1367 characters in body
Aug
21
revised strange “bad file descriptor” error
simplified demo script
Aug
21
revised strange “bad file descriptor” error
added 281 characters in body
Aug
21
asked strange “bad file descriptor” error
Aug
17
comment Absolute path to currently-running zsh?
Thanks! BTW, on my system, the last two gave different answers, because the one given by the second is a symlink; I had to run sudo /bin/ls -l $( whence -p -- ${0#-} ) to get the true path (which then agreed with the results of the lsof approach).
Aug
17
accepted Absolute path to currently-running zsh?
Aug
17
comment zsh and COLUMNS
@StephaneChazelas: Thanks! That certainly takes care of (1). (BTW, this is the reason for my other question, about finding the path the currently-running zsh.)
Aug
16
asked zsh and COLUMNS
Aug
16
revised Absolute path to currently-running zsh?
added 109 characters in body
Aug
16
comment Absolute path to currently-running zsh?
@StephaneChazelas: Darwin; and the ps I'm using above is /bin/ps. For good measure, I ran /bin/ps -p $$, and got the same output as shown above.
Aug
16
asked Absolute path to currently-running zsh?