Comments on: Shell tricks: shorthands http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/ Random Computer Musings Thu, 20 Nov 2008 22:05:17 +0000 http://wordpress.org/?v=2.5.1 By: Alexandre http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-218 Alexandre Fri, 19 Oct 2007 13:36:55 +0000 http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-218 <p>Azrael, I think you missed the point of my aliases. It is not for making the command easier to remember, but simply to make them shorter and easier to type. Although, I have to admit <code>wajig</code> looks like neat little wrapper. Thanks.</p> Azrael, I think you missed the point of my aliases. It is not for making the command easier to remember, but simply to make them shorter and easier to type. Although, I have to admit wajig looks like neat little wrapper. Thanks.

]]> By: Alexandre http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-212 Alexandre Fri, 19 Oct 2007 13:25:29 +0000 http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-212 <p>bartman, Zsh's extended globing feature is kinda neat, but it sucks for searching through many files:</p> <pre><code>% grep ^malloc src/**/*.[ch] zsh: argument list too long: grep </code></pre> <p>It is basically equivalent to:</p> <pre><code>% grep ^malloc `find src/ -name '*.[ch]'` </code></pre> <p>Personally, I like to keep the amount of meta-characters at a minimum. So, I would prefer using the <code>find</code> version.</p> bartman, Zsh’s extended globing feature is kinda neat, but it sucks for searching through many files:

% grep ^malloc src/**/*.[ch]
zsh: argument list too long: grep

It is basically equivalent to:

% grep ^malloc `find src/ -name '*.[ch]‘`

Personally, I like to keep the amount of meta-characters at a minimum. So, I would prefer using the find version.

]]> By: Azrael Nightwalker http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-215 Azrael Nightwalker Fri, 19 Oct 2007 10:43:21 +0000 http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-215 <p>Use wajig and you won't have to set up many of those aliases.</p> Use wajig and you won’t have to set up many of those aliases.

]]> By: Pete http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-217 Pete Thu, 18 Oct 2007 18:44:11 +0000 http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-217 <p>One feature I really miss in *buntu is history-search-backward/forward in bash. This is where you are able to start typing a command, press page up or down (default keys I like) and it completes it with commands from your history which match what you've typed so far.</p> <p>System wide way to enable it is to un-comment the two lines shown below,</p> <p>"e[5~": history-search-backward</p> <p>"e[6~": history-search-forward</p> <p>Great feature, not sure why its disabled by default!</p> One feature I really miss in *buntu is history-search-backward/forward in bash. This is where you are able to start typing a command, press page up or down (default keys I like) and it completes it with commands from your history which match what you’ve typed so far.

System wide way to enable it is to un-comment the two lines shown below,

“e[5~”: history-search-backward

“e[6~”: history-search-forward

Great feature, not sure why its disabled by default!

]]> By: Zamber http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-213 Zamber Thu, 18 Oct 2007 17:41:54 +0000 http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-213 <p>Send a info to Lifehacker.com! A couple months ago they had some tweaking like this described but it wasn't so advanced ;).</p> Send a info to Lifehacker.com! A couple months ago they had some tweaking like this described but it wasn’t so advanced ;).

]]> By: bartman http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-214 bartman Thu, 18 Oct 2007 16:50:19 +0000 http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-214 <p>Looks like you're missing the '**' zsh trick.</p> <pre><code>% find Lib/ -name '*.c' -print0 | xargs -0 grep ^PyErr</code></pre> <p>can be rewritten as</p> <pre><code>% grep \^PyErr Lib/**/*.c</code></pre> <p>With ** zsh will do all the hard work of finding the files. Note however that I had to escape ^, because in zsh it means "match everything but ...". Alternatively you can put your match expression in quotes.</p> Looks like you’re missing the ‘**’ zsh trick.

% find Lib/ -name '*.c' -print0 | xargs -0 grep ^PyErr

can be rewritten as

% grep \^PyErr Lib/**/*.c

With ** zsh will do all the hard work of finding the files. Note however that I had to escape ^, because in zsh it means “match everything but …”. Alternatively you can put your match expression in quotes.

]]> By: Matt Galvin http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-216 Matt Galvin Thu, 18 Oct 2007 16:47:50 +0000 http://peadrop.com/blog/2007/10/18/shell-tricks-shorthands/#comment-216 <p>Great post!</p> <p>Something I like to do with Type-A commands is rather then an alias of <code>spkgi</code>, I use an alias of <code>install</code>, <code>upgrade</code>, <code>remove</code>, etc... simple verbs that even less experienced users would easily understand how to use. So we get:</p> <p>install banshee install apache2</p> <p>and the like. Very easy to understand and remember, IMHO.</p> Great post!

Something I like to do with Type-A commands is rather then an alias of spkgi, I use an alias of install, upgrade, remove, etc… simple verbs that even less experienced users would easily understand how to use. So we get:

install banshee install apache2

and the like. Very easy to understand and remember, IMHO.

]]>