Now on ScienceBlogs: The 1/6th People

Seed Media Group

Collective Imagination

Greg Laden's Blog

Evolution, Life Sciences, Science Education, Human Evolution, and Stuff

Recent Comments

Profile


Welcome to Greg Laden's Blog.




Nature Blog Network



Search

Join the best atheist themed blogroll!

Archives

Recent Posts

« Ooops ... gun goes off on commercial plane | Main | New early human fossil »

Learning the bash shell, third look

Posted on: March 26, 2008 6:52 PM, by Greg Laden

image.jpgTime for another installment of our look at the book Learning the bash Shell (In a Nutshell (O'Reilly)). Today's foray into Linux Land: Unix Command Substitution.

There is more than one way to do this, but here is a sensible way to look at the format. In command substitution you stick something that comes out to be a valid UNIX command insice parentheses preceded with a dollar sign:

$(UNIX command)

The unix command is evaluated and then the result replaces the $() bit.

For example, say you wanted to edit all of the files in the current directory that included the letters "html". You could use the "grep" command to parse out all of the files to get a look at them. Grep goes through files and searches for a string, and by default spits out the line containing the string. There is an option (-l) that tells grep to spit out only the filename. So, for instance, I can do this:


greg@greg-desktop:~/Desktop$ cd markdown
greg@greg-desktop:~/Desktop/markdown$ grep -l 'html' *
4sh.html
blog2.html
blog2.txt
blogrolJava.txt
blogroll_master_SU
boneyard.html
boneyard.txt
calendar2html
debate2.html

...

Then I could type these names into the text editor command.

Or, I can turn this list of phrases into part of a command line. If I use "getdit" as the text editor, I can type"

gedit grep -l 'html' *

But that would not work! -l is not an available option for gedit, and there are other confusing things on this line to cause gedit to not get it. Get it? Good.

BUt, if I put the mojo that spits out the list of files (which I tried above and know works) into the command sbustitution command, then then that will convert "grep -l 'html' *" into a a list of files.

So this works:


greg@greg-desktop:~/Desktop/markdown$ gedit $(grep -l html *) &

This is the same as typing:

greg@greg-desktop:~/Desktop/markdown$ gedit 4sh.html blog2.html blog2.txt .... and so on. The "and" sign at the end puts the operation into the background so I can keep using the same command line.


Share this: Stumbleupon Reddit Email + More

TrackBacks

TrackBack URL for this entry: http://scienceblogs.com/mt/pings/67704

Comments

1

How about "grep -l 'html' * > filename.txt"?

Posted by: Max Dobberstein | March 26, 2008 9:01 PM

2

Well, the goal is to edit the files that have html in them, not to edit a list of names of files that have html in them.

But
grep -l 'html' * | xargs gedit &
will work for many people who don't have bash as their shell.

Posted by: rpenner | March 26, 2008 9:42 PM

Post a Comment

(Email is required for authentication purposes only. On some blogs, comments are moderated for spam, so your comment may not appear immediately.)





ScienceBlogs

Search ScienceBlogs:

Go to:

Advertisement
Enter to win a free copy of The Monty Hall Problem
Visit the Collective Imagination blog
Advertisement
Collective Imagination

© 2006-2009 Seed Media Group LLC. ScienceBlogs is a registered trademark of Seed Media Group. All rights reserved.

Sites by Seed Media Group: Seed Media Group | ScienceBlogs | SEEDMAGAZINE.COM