385 reputation
313
bio website
location United States
age
visits member for 4 years, 5 months
seen yesterday

Jun
30
comment colorized bash prompt overwrites previous command's output if the output doesn't end with a newline
Unfamiliar with PROMPT_COMMAND. I've just been setting PS1. unset PROMPT_COMMAND doesn't help. $ echo $PROMPT_COMMAND gives echo -ne "\033_${USER}@${HOSTNAME%%.*}:${PWD/#$HOME/~}"; echo -ne "\033\\"
Jun
30
revised colorized bash prompt overwrites previous command's output if the output doesn't end with a newline
added bash version info
Jun
22
revised colorized bash prompt overwrites previous command's output if the output doesn't end with a newline
made example colorized prompt less confusing
Jun
22
asked colorized bash prompt overwrites previous command's output if the output doesn't end with a newline
Jun
20
answered Unix: How to unsplit in screen
Jan
15
comment mac os x, find all symbolic links that point to files on a different volume
Good job finding that workaround!
Jan
15
accepted mac os x, find all symbolic links that point to files on a different volume
Jan
14
asked mac os x, find all symbolic links that point to files on a different volume
Nov
17
answered Microsoft keyboard media keys on OS X without Microsoft's Drivers
Nov
12
answered Any way to fix screen's mishandling of line wrap? (Maybe only Terminal.app)
Nov
3
comment Any way to fix screen's mishandling of line wrap? (Maybe only Terminal.app)
Also, this isn't a problem in iTerm.app
Nov
3
comment Any way to fix screen's mishandling of line wrap? (Maybe only Terminal.app)
At any time it starts to go bad, just select all (COMMAND+A) to make the screen buffer look right.
Oct
28
revised How do I make CMD+? work the native way with Firefox for Mac?
swap "cmd" with "⌘"
Oct
28
comment Any way to fix screen's mishandling of line wrap? (Maybe only Terminal.app)
didn't help it in my case.
Oct
28
awarded  Commentator
Oct
28
comment Any way to fix screen's mishandling of line wrap? (Maybe only Terminal.app)
I have the exact same behavior. Another symptom of it (not described above) is that after the previous line is 'eaten', strange things happen with selections. Start selecting with the mouse, and whatever is under the selection will appear correct. Ex: if you were to select the "$ asdf" line in the last example above, it would suddenly change to "bash: asdf: command not found" (which is what the previous line should say.) It's as if the screen just hasn't re-drawn those lines, but should have. It's like it's forgetting to mark those lines as dirty, needing to be re-rendered.
Oct
22
comment How do I make CMD+? work the native way with Firefox for Mac?
I now see there are some textual instructions indicating that the shortcuts can be edited on that pref pane.
Oct
21
comment How do I make CMD+? work the native way with Firefox for Mac?
I didn't even know shortcuts in System Preferences > Keyboard Shortcuts > Application Shortcuts could be edited! Nice! (There is no visual indication that they can be edited.)
Oct
21
accepted How do I make CMD+? work the native way with Firefox for Mac?
Oct
21
asked How do I make CMD+? work the native way with Firefox for Mac?