Favorite Unix Commands • Hacker News Board

Re: Favorite Unix Commands

#51

Post by donquix » Mon, Jan 07, 2013, 10:41 PM UTC

sudo !!

Instant favorite

Re: Favorite Unix Commands

#52

Post by ralph » Mon, Jan 07, 2013, 10:42 PM UTC

MikeCodeAwesome wrote: post #46

SkippyZA wrote: post #21

Ctrl+l is my most used command. I need a clean terminal

Same here; and love that it doesn't clear the command line you're currently typing. Does anyone know if there's a key command for clearing the scroll buffer?

yes(1).

Re: Favorite Unix Commands

#53

Post by emillon » Mon, Jan 07, 2013, 10:44 PM UTC

ralph wrote: post #50

overgun77 wrote: post #47

Not really a unix command, but a vi command that has been really useful, specially if you do lots of editing protected files and want to keep your custom vim configuration: !sudo tee %

What vi mode is that entered in?

Normal mode (:help :! for more information on this command).

Re: Favorite Unix Commands

#54

Post by t_lark » Mon, Jan 07, 2013, 10:44 PM UTC

grep -r . "Some random debug msg"

Re: Favorite Unix Commands

#55

Post by nickwoodhams » Mon, Jan 07, 2013, 10:46 PM UTC

vog wrote: post #48

There's a typo: The command is spelled "apropos" (not apropo).

Corrected this typo. Thanks.

Re: Favorite Unix Commands

#56

Post by ralph » Mon, Jan 07, 2013, 10:47 PM UTC

cjg_ wrote: post #31

jfb wrote: post #27

Earlier quoted context omitted.

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.

Hm, can you start at the end of file without reading the entire file with less? Use case is tailing large logs.

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.

Re: Favorite Unix Commands

#57

Post by tlarkworthy » Mon, Jan 07, 2013, 10:47 PM UTC

grep -r . "some random debug message" (searches for the passage recursively in all files from the directory it was executed, the main reason I like developing in linux more than windows)

Re: Favorite Unix Commands

#58

Post by ralph » Mon, Jan 07, 2013, 10:49 PM UTC

emillon wrote: post #53

ralph wrote: post #50

Earlier quoted context omitted.

What vi mode is that entered in?

Normal mode (:help :! for more information on this command).

What benefit does

    :!sudo tee %

have over doing it at the command line other than filling in the current filename for you? I suspect the original poster meant something like "gg!Gsudo tee %".

Re: Favorite Unix Commands

#59

Post by ralph » Mon, Jan 07, 2013, 10:50 PM UTC

VaucGiaps wrote: post #26

gav wrote: post #14

Earlier quoted context omitted.

Using `find` is nice to get just directories: $ find . -type d -maxdepth 1

ls -al | grep ^d

(Fails if a directory has a linefeed in its name followed by a 'd'. :-)

Re: Favorite Unix Commands

#60

Post by jlgreco » Mon, Jan 07, 2013, 10:52 PM UTC

tlarkworthy wrote: post #57

grep -r . "some random debug message" (searches for the passage recursively in all files from the directory it was executed, the main reason I like developing in linux more than windows)

If you are searching inside code specifically, you may like 'ack'. It does the same thing grep does, except it has preset 'excludes', is recursive by default, and the output is a bit prettier.