man hier is pretty cool. It explains the root directory structure of the system.
"apropos Regular Expressions" brings up wild stuff: re_format(7) -- posix regex docs at last!, treereg(1) (huh????).
Some serious lore in here ...
111–120 of 166 posts
man hier is pretty cool. It explains the root directory structure of the system.
"apropos Regular Expressions" brings up wild stuff: re_format(7) -- posix regex docs at last!, treereg(1) (huh????).
Some serious lore in here ...
You know what I hate? My history isn't aggregated in real time across all my Mac OS X terminal windows. You know what else I hate? Typing in long commands in the Mac OS X terminal and then them wrapping weirdly. Especially when I hit the up arrow to go back in my terminal history.
> In bash, 'ctrl-r' searches your command history No! In emacs ctrl-r searches your command history. It happens that bash use emacs mode by default. All other emacs basic commands work too: ctrl-p, ctrl-n, ctrl-f etc... If you are a vim user, and especially if you love venting how much you hate emacs, then please add this to your bashrc: set -o vi and now you can use vim command instead of emacs.
'ctrl-r' is reverse-i-search in vi mode as well.
'meta-r' is bound to comint-history-isearch-backward-regexp
E.g echo "This would be contents of file" | someCommand /dev/fd/0
Earlier quoted context omitted.
Caution: while this works great on Linux, on OSX, a USR1 will kill dd, and a SIGINFO will get you the block counts.
Indeed, looks like GNU coreutils dd responds to SIGUSR1 on linux and SIGINFO on linux. That's good to know. What's the reason for this discrepancy?
Linux doesn't. I don't know why; but Google in the past has told me that patches to add it were rejected about 10 years ago.
You know what I hate? My history isn't aggregated in real time across all my Mac OS X terminal windows. You know what else I hate? Typing in long commands in the Mac OS X terminal and then them wrapping weirdly. Especially when I hit the up arrow to go back in my terminal history.
> Typing in long commands in the Mac OS X terminal and then them wrapping weirdly. For all people who dont use Mac OS X: This happens because your PS1 is wrongly set and bash cant calculate correctly the length left of your line. Try it out, by going back to default with no colors and crap and see how long it goes. For mac os x users. The above wont help, dont even try it.