8 ms·

Please comment if you have a favorite not on this list.

by nickwoodhams 14y ago

asparagui 14y ago
alias emacs="nano"
- deleted 14y ago
  [deleted]
- GrumpySimon 14y ago
  export EDITOR=/usr/bin/nano
- zacharystern 14y ago
  nooooooo!
jlgreco 14y ago
'tac'. It is 'cat', but backwards.
- SenorWilson 14y ago
  Are you some kind of genius?
  - jlgreco 14y ago
    If you enjoy 'tac', you might also enjoy 'sponge'. Spong 'soaks up' input an releases it all on one chunk so that you can do things like: cat foo | sponge foo (`cat foo > foo` does not work) That's neat and all, but what if you don't have sponge? Well, just use tac twice! cat foo | tac | tac > foo (Obviously this is rather wasteful ;))
    - thristian 14y ago
      I cannot understand how this works. "cat foo > foo" breaks, because the shell truncates the file "foo" while it's setting up the redirection, before it launches "cat foo", and so cat has nothing to read. "cat foo | sponge foo" works because the shell is not responsible for writing to foo; it launches cat (which opens the file for reading) then launches sponge (which eventually opens the file for writing). I would thus expect "cat foo | tac | tac > foo" to fail in the same way as "cat foo > foo" because the shell is still going to open the file foo and truncate it, but experimentation shows that it does actually work. Is it because the shell launches each pipeline one at a time, so cat has read the file before "tac > foo" truncates it? Is it a race-condition or a corner-case?
      - deleted 14y ago
        [deleted]
      - jlgreco 14y ago
        That's a good question. I had though it worked because the truncate would not actually happen until tac actually wrote something, but now that I look at it more I don't think that is actually the case. `cat > foo` immediately truncates foo before anything is written. Also `tac foo > foo` doesn't work, which discredits my hypothesis that tac's buffering was causing it. Furthermore `cat foo | cat > foo` does not work, but `cat foo | cat | cat > foo` does work. I suspect this behavior is actually a race condition of some sort. Edit: definetly a race condition, shown by larger files: % wc -l foo 1310720 foo % cat foo | cat | cat > foo % wc -l foo 16384 1
- thristian 14y ago
  I always get confused between "tac" and "rev", which is also "cat, but backwards" for a certain definition of "backwards".
lelf 14y ago
dtrace :P
codegeek 14y ago
alias lsd="ls -ltrF | grep ^d" Helps me quickly list only directories. Any better alternatives ?
- gav 14y ago
  Using `find` is nice to get just directories: $ find . -type d -maxdepth 1
  - VaucGiaps 14y ago
    ls -al | grep ^d
    - ralph 14y ago
      (Fails if a directory has a linefeed in its name followed by a 'd'. :-)
  - pnrao 14y ago
    I use: % ls -d */
  - deleted 14y ago
    [deleted]
- lneves 14y ago
  find . -type d edit: for the same output as your command you can use: dir -l
- williadc 14y ago
  Dunno what "better" means, but this also works: find -maxdepth 1 -type d
  - mttsn 14y ago
    seconded. what I have always used
- jfb 14y ago
jfb 14y ago
tsort. It's pointless until you need it, but when you need it, it's totally awesome. less. Overkill, but SO MUCH BETTER THAN tail -f. Seriously. You can toggle "follow mode" without losing your place in the incoming stream.
- cjg_ 14y ago
  Hm, can you start at the end of file without reading the entire file with less? Use case is tailing large logs.
  - jfb 14y ago
    Yes. It is CPU intensive (see auntie post above).
  - ralph 14y ago
    Yes, either type G when presented with the top of the file or pass +G on the command line. It will then read all the intervening file to calculate the line numbers, and tells you it's doing this and to interrupt it to stop. To prevent it doing this in the first place use the -n option. "less -n huge_file" and then G only reads the start and end of the file. Type G again to move to the latest end of the file if it's growing.
- Florin_Andrei 14y ago
  > less. Overkill, but SO MUCH BETTER THAN tail -f. Seriously. If you do this on my servers, I am going to find you, and then I am going to kill... um... your process. less with SHIFT-F takes a whole CPU core to run on a busy log file. tail -f takes almost nothing to run. Now combine that information with the reality of a whole bunch of devs who don't know it or don't care about it. :(
- mje__ 14y ago
  multitail[1] is also really nice for following multiple log files. It can do highlighting of lines based on regex's, and has built-in highlighting of a wide variety of log formats [1] http://www.vanheusden.com/multitail/features.php http://www.vanheusden.com/multitail/features.php
cnvogel 14y ago
When rewriting large amounts of ASCII text (or comments in Code), I really find "par" helpful. : Just use it in : : vi with your cursor in front of a badly wrapped block of text. : : Press !}par<enter> and the text will be : : piped to par : : which fixes up : : the : : formatting and keeps aligned frame markers : : intact magically. : : Just use it in vi with your cursor in front of a badly wrapped : : block of text. Press !}par<enter> and the text will be piped : : to par which fixes up the formatting and keeps aligned frame : : markers intact magically. : http://www.nicemice.net/par/ http://www.nicemice.net/par/ (or apt-get install par)
- satiani 14y ago
  Or you can just select the block of text and type gq. This will do what par does, and can be adjusted with vim's 'textwidth' and 'formatoptions' settings.
cnvogel 14y ago
If you use tmux (or screen) you want to use byobu! https://launchpad.net/byobu https://launchpad.net/byobu https://www.google.de/search?q=byobu+tmux&tbm=isch https://www.google.de/search?q=byobu+tmux&tbm=isch It's a fancy statusbar that shows CPU speed, IP-address, hostname, ...
- vially 14y ago
  Another option is tmux-powerline[1] [1] https://github.com/erikw/tmux-powerline https://github.com/erikw/tmux-powerline
- jsaxton86 14y ago
  You can get a fancy status bar with screen, you just need a screenrc file: http://www.mbeckler.org/blog/2012/11/28/my-screenrc-file-circa-2012/ http://www.mbeckler.org/blog/2012/11/28/my-screenrc-file-cir...
- tkahn6 14y ago
  I have something similar in my .tmux.conf file Screenshot: http://i.imgur.com/u6JY0.png http://i.imgur.com/u6JY0.png Config file: https://github.com/tylerkahn/dotfiles/blob/master/.tmux.conf#L49 https://github.com/tylerkahn/dotfiles/blob/master/.tmux.conf... Works with OSX and Linux.
zeraholladay 14y ago
export CDPATH=.:~/projects export PS1="$(uname -n)$ " alias ltr='ls -ltr' More of a procedure, always list file and edit the command before deleting it: $ ll file.txt -rw-r--r-- 1 zera staff 0 Jan 7 20:28 file.txt Ctrl-p, Ctrl-a, Ctrl-d, Ctrl-d, r,m $ rm file.txt So this is a sanity check to avoid this mistake: $ rm *.txt *Edit, one more: Ensure you overwrite a file (or aren't): $ cp -i ~/file.config /etc/
mappu 14y ago
sl

Please comment if you have a favorite not on this list.

asparagui 14y ago

alias emacs="nano"

deleted 14y ago
[deleted]
GrumpySimon 14y ago
export EDITOR=/usr/bin/nano
zacharystern 14y ago
nooooooo!

jlgreco 14y ago

'tac'. It is 'cat', but backwards.

SenorWilson 14y ago
Are you some kind of genius?
- jlgreco 14y ago
  If you enjoy 'tac', you might also enjoy 'sponge'. Spong 'soaks up' input an releases it all on one chunk so that you can do things like: cat foo | sponge foo (`cat foo > foo` does not work) That's neat and all, but what if you don't have sponge? Well, just use tac twice! cat foo | tac | tac > foo (Obviously this is rather wasteful ;))
  - thristian 14y ago
    I cannot understand how this works. "cat foo > foo" breaks, because the shell truncates the file "foo" while it's setting up the redirection, before it launches "cat foo", and so cat has nothing to read. "cat foo | sponge foo" works because the shell is not responsible for writing to foo; it launches cat (which opens the file for reading) then launches sponge (which eventually opens the file for writing). I would thus expect "cat foo | tac | tac > foo" to fail in the same way as "cat foo > foo" because the shell is still going to open the file foo and truncate it, but experimentation shows that it does actually work. Is it because the shell launches each pipeline one at a time, so cat has read the file before "tac > foo" truncates it? Is it a race-condition or a corner-case?
    - deleted 14y ago
      [deleted]
    - jlgreco 14y ago
      That's a good question. I had though it worked because the truncate would not actually happen until tac actually wrote something, but now that I look at it more I don't think that is actually the case. `cat > foo` immediately truncates foo before anything is written. Also `tac foo > foo` doesn't work, which discredits my hypothesis that tac's buffering was causing it. Furthermore `cat foo | cat > foo` does not work, but `cat foo | cat | cat > foo` does work. I suspect this behavior is actually a race condition of some sort. Edit: definetly a race condition, shown by larger files: % wc -l foo 1310720 foo % cat foo | cat | cat > foo % wc -l foo 16384 1
thristian 14y ago
I always get confused between "tac" and "rev", which is also "cat, but backwards" for a certain definition of "backwards".

lelf 14y ago

dtrace :P

codegeek 14y ago

alias lsd="ls -ltrF | grep ^d" Helps me quickly list only directories. Any better alternatives ?

gav 14y ago
Using `find` is nice to get just directories: $ find . -type d -maxdepth 1
- VaucGiaps 14y ago
  ls -al | grep ^d
  - ralph 14y ago
    (Fails if a directory has a linefeed in its name followed by a 'd'. :-)
- pnrao 14y ago
  I use: % ls -d */
- deleted 14y ago
  [deleted]
lneves 14y ago
find . -type d edit: for the same output as your command you can use: dir -l
williadc 14y ago
Dunno what "better" means, but this also works: find -maxdepth 1 -type d
- mttsn 14y ago
  seconded. what I have always used
jfb 14y ago

jfb 14y ago

tsort. It's pointless until you need it, but when you need it, it's totally awesome. less. Overkill, but SO MUCH BETTER THAN tail -f. Seriously. You can toggle "follow mode" without losing your place in the incoming stream.

cjg_ 14y ago
Hm, can you start at the end of file without reading the entire file with less? Use case is tailing large logs.
- jfb 14y ago
  Yes. It is CPU intensive (see auntie post above).
- ralph 14y ago
  Yes, either type G when presented with the top of the file or pass +G on the command line. It will then read all the intervening file to calculate the line numbers, and tells you it's doing this and to interrupt it to stop. To prevent it doing this in the first place use the -n option. "less -n huge_file" and then G only reads the start and end of the file. Type G again to move to the latest end of the file if it's growing.
Florin_Andrei 14y ago
> less. Overkill, but SO MUCH BETTER THAN tail -f. Seriously. If you do this on my servers, I am going to find you, and then I am going to kill... um... your process. less with SHIFT-F takes a whole CPU core to run on a busy log file. tail -f takes almost nothing to run. Now combine that information with the reality of a whole bunch of devs who don't know it or don't care about it. :(
mje__ 14y ago
multitail[1] is also really nice for following multiple log files. It can do highlighting of lines based on regex's, and has built-in highlighting of a wide variety of log formats [1] http://www.vanheusden.com/multitail/features.php http://www.vanheusden.com/multitail/features.php

cnvogel 14y ago

When rewriting large amounts of ASCII text (or comments in Code), I really find "par" helpful. : Just use it in : : vi with your cursor in front of a badly wrapped block of text. : : Press !}par<enter> and the text will be : : piped to par : : which fixes up : : the : : formatting and keeps aligned frame markers : : intact magically. : : Just use it in vi with your cursor in front of a badly wrapped : : block of text. Press !}par<enter> and the text will be piped : : to par which fixes up the formatting and keeps aligned frame : : markers intact magically. : http://www.nicemice.net/par/ http://www.nicemice.net/par/ (or apt-get install par)

satiani 14y ago
Or you can just select the block of text and type gq. This will do what par does, and can be adjusted with vim's 'textwidth' and 'formatoptions' settings.

cnvogel 14y ago

If you use tmux (or screen) you want to use byobu! https://launchpad.net/byobu https://launchpad.net/byobu https://www.google.de/search?q=byobu+tmux&tbm=isch https://www.google.de/search?q=byobu+tmux&tbm=isch It's a fancy statusbar that shows CPU speed, IP-address, hostname, ...

vially 14y ago
Another option is tmux-powerline[1] [1] https://github.com/erikw/tmux-powerline https://github.com/erikw/tmux-powerline
jsaxton86 14y ago
You can get a fancy status bar with screen, you just need a screenrc file: http://www.mbeckler.org/blog/2012/11/28/my-screenrc-file-circa-2012/ http://www.mbeckler.org/blog/2012/11/28/my-screenrc-file-cir...
tkahn6 14y ago
I have something similar in my .tmux.conf file Screenshot: http://i.imgur.com/u6JY0.png http://i.imgur.com/u6JY0.png Config file: https://github.com/tylerkahn/dotfiles/blob/master/.tmux.conf#L49 https://github.com/tylerkahn/dotfiles/blob/master/.tmux.conf... Works with OSX and Linux.

zeraholladay 14y ago

export CDPATH=.:~/projects export PS1="$(uname -n)$ " alias ltr='ls -ltr' More of a procedure, always list file and edit the command before deleting it: $ ll file.txt -rw-r--r-- 1 zera staff 0 Jan 7 20:28 file.txt Ctrl-p, Ctrl-a, Ctrl-d, Ctrl-d, r,m $ rm file.txt So this is a sanity check to avoid this mistake: $ rm *.txt *Edit, one more: Ensure you overwrite a file (or aren't): $ cp -i ~/file.config /etc/

mappu 14y ago