<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 10 Linux Commands You Probably Don&#8217;t Use</title>
	<atom:link href="http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/</link>
	<description>Linux Tips, Tricks, and Opinions</description>
	<lastBuildDate>Wed, 27 Jun 2012 07:49:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: canuck</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-195403</link>
		<dc:creator>canuck</dc:creator>
		<pubDate>Fri, 06 Jan 2012 00:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-195403</guid>
		<description>One of my favourites is still pushd and popd; these are used to push items (such as the current directory) on or off the of stack.

Ex:
[/home/username] # pushd .
[/home/username] # cd /usr/bin
[/usr/bin] # popd
[/home/username] #</description>
		<content:encoded><![CDATA[<p>One of my favourites is still pushd and popd; these are used to push items (such as the current directory) on or off the of stack.</p>
<p>Ex:<br />
[/home/username] # pushd .<br />
[/home/username] # cd /usr/bin<br />
[/usr/bin] # popd<br />
[/home/username] #</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: skeruno</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-40969</link>
		<dc:creator>skeruno</dc:creator>
		<pubDate>Sat, 13 Jun 2009 09:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-40969</guid>
		<description>With Ctrl+e you wil go the end of the line. thats easy if you for example typed the following :

# xd /home/testuser/somedir

you see there&#039;s a typo ( xd instead of cd ) to easyly fix this with out starting over again ( ctrl+c ), press ctrl+a which will take the cursor to the beginning of the line to make your change ( xd to cd ). 
then go to the end of the line with ctrl+e. 
and lets say you changed your mind about going to the dir in the testuser&#039;s homedir. lets say you wantes to go to /usr/src instead. 
You can use ctrl+w to delete the argument backwards from the point where the cursor is.
so in our example you pressed ctrl+e to go to the and of the line. now ctrl+w will delete &quot;/home/testuser/somedir&quot; so you can replace it with /usr/src ( using TAB to speed it up ) 

so how to be really fast with this combined with your command history? here&#039;s an example:

# mkdir /tmp/foo
# cp ~/somefile [esc-.] 
esc-. will return the last argument of the previous commando, same as alt-.
# 
ctrl+r and type &#039;mk&#039; that will bring up the last command wich contains &#039;mk&#039; in this case our last mkdir commando
# mkdir /tmp/foo [ ctrl+w ]
ctrl+w will remove the /tmp/foo
# mkdir /usr/src/bar
# cd [esc-.]

these are short examples. most of the time when you have long oneliners you don&#039;t want to type the all over or wait for the cursor to get the the beginning of the line. 

keep in mind that these are bash shortcuts. i dont know which will but as far as i know most will not work in an other shell like sh, ksh or csh 

read man bash if you want to know more to be faster and more efficient 

regards,

Vincent</description>
		<content:encoded><![CDATA[<p>With Ctrl+e you wil go the end of the line. thats easy if you for example typed the following :</p>
<p># xd /home/testuser/somedir</p>
<p>you see there&#8217;s a typo ( xd instead of cd ) to easyly fix this with out starting over again ( ctrl+c ), press ctrl+a which will take the cursor to the beginning of the line to make your change ( xd to cd ).<br />
then go to the end of the line with ctrl+e.<br />
and lets say you changed your mind about going to the dir in the testuser&#8217;s homedir. lets say you wantes to go to /usr/src instead.<br />
You can use ctrl+w to delete the argument backwards from the point where the cursor is.<br />
so in our example you pressed ctrl+e to go to the and of the line. now ctrl+w will delete &#8220;/home/testuser/somedir&#8221; so you can replace it with /usr/src ( using TAB to speed it up ) </p>
<p>so how to be really fast with this combined with your command history? here&#8217;s an example:</p>
<p># mkdir /tmp/foo<br />
# cp ~/somefile [esc-.]<br />
esc-. will return the last argument of the previous commando, same as alt-.<br />
#<br />
ctrl+r and type &#8216;mk&#8217; that will bring up the last command wich contains &#8216;mk&#8217; in this case our last mkdir commando<br />
# mkdir /tmp/foo [ ctrl+w ]<br />
ctrl+w will remove the /tmp/foo<br />
# mkdir /usr/src/bar<br />
# cd [esc-.]</p>
<p>these are short examples. most of the time when you have long oneliners you don&#8217;t want to type the all over or wait for the cursor to get the the beginning of the line. </p>
<p>keep in mind that these are bash shortcuts. i dont know which will but as far as i know most will not work in an other shell like sh, ksh or csh </p>
<p>read man bash if you want to know more to be faster and more efficient </p>
<p>regards,</p>
<p>Vincent</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vinas</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-25407</link>
		<dc:creator>Vinas</dc:creator>
		<pubDate>Tue, 07 Oct 2008 12:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-25407</guid>
		<description>What about the built in ps and grep? Surely it&#039;s better to know how to use grep with other commands...   ps -ax &#124;grep fox</description>
		<content:encoded><![CDATA[<p>What about the built in ps and grep? Surely it&#8217;s better to know how to use grep with other commands&#8230;   ps -ax |grep fox</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ForiPepe</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-25316</link>
		<dc:creator>ForiPepe</dc:creator>
		<pubDate>Sun, 05 Oct 2008 17:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-25316</guid>
		<description>If you are in a terminal, and you use a command, it occupies the terminal:
gedit somefile
If you use &amp; at the end of the command, you can run the program and use the terminal in the same time:
gedit somefile&amp;
If you forget to put &amp; on the end of the command, and you would like to use the terminal without closing the application, press:
CTRL-z
The job stopped. You will see something like this:
[1]+  Stopped                 gedit somefile
Where 1 is the job specifier.
After that you can start the job with:
fg 1
and your terminal will be reserved again. Or you can use:
bg 1
and your program and the terminal will be available in the same time.</description>
		<content:encoded><![CDATA[<p>If you are in a terminal, and you use a command, it occupies the terminal:<br />
gedit somefile<br />
If you use &amp; at the end of the command, you can run the program and use the terminal in the same time:<br />
gedit somefile&amp;<br />
If you forget to put &amp; on the end of the command, and you would like to use the terminal without closing the application, press:<br />
CTRL-z<br />
The job stopped. You will see something like this:<br />
[1]+  Stopped                 gedit somefile<br />
Where 1 is the job specifier.<br />
After that you can start the job with:<br />
fg 1<br />
and your terminal will be reserved again. Or you can use:<br />
bg 1<br />
and your program and the terminal will be available in the same time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ATOzTOA</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-18840</link>
		<dc:creator>ATOzTOA</dc:creator>
		<pubDate>Fri, 27 Jun 2008 13:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-18840</guid>
		<description>Actually, I never knew most of these tips, I use CLI often... thx bud

You can save and exit vi by :x ....  easier than shift+w+w</description>
		<content:encoded><![CDATA[<p>Actually, I never knew most of these tips, I use CLI often&#8230; thx bud</p>
<p>You can save and exit vi by <img src='http://www.foogazi.com/wp-includes/images/smilies/icon_mad.gif' alt=':x' class='wp-smiley' />  &#8230;.  easier than shift+w+w</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yeah_boy</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-18033</link>
		<dc:creator>yeah_boy</dc:creator>
		<pubDate>Sat, 14 Jun 2008 17:23:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-18033</guid>
		<description>I don&#039;t use the command line much (I am one of those relatively new linux users), but I did learn something from this post and the comments.

@Ricardo Figueroa:
Couldn&#039;t you use {mkdir dir &amp;&amp; cd $_} instead of {mkdir dir &amp;&amp; cd dir} so as to avoid having to re-type the directory name -- which you could possibly mis-type the second time?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t use the command line much (I am one of those relatively new linux users), but I did learn something from this post and the comments.</p>
<p>@Ricardo Figueroa:<br />
Couldn&#8217;t you use {mkdir dir &amp;&amp; cd $_} instead of {mkdir dir &amp;&amp; cd dir} so as to avoid having to re-type the directory name &#8212; which you could possibly mis-type the second time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10 comandos de Linux que tal vez no usas</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-17882</link>
		<dc:creator>10 comandos de Linux que tal vez no usas</dc:creator>
		<pubDate>Wed, 11 Jun 2008 05:23:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-17882</guid>
		<description>[...] de foogazi.com  Fin del articulo    Esta entrada fue escrita por Casidiablo, publicada en Junio 11, 2008 at 1:23 [...]</description>
		<content:encoded><![CDATA[<p>[...] de foogazi.com  Fin del articulo    Esta entrada fue escrita por Casidiablo, publicada en Junio 11, 2008 at 1:23 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ketan</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-17740</link>
		<dc:creator>ketan</dc:creator>
		<pubDate>Sun, 08 Jun 2008 21:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-17740</guid>
		<description>ctrl+l will clear the screen.</description>
		<content:encoded><![CDATA[<p>ctrl+l will clear the screen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-17628</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Fri, 06 Jun 2008 12:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-17628</guid>
		<description>When the title says &quot;10 Linux Commands You Probably Don’t Use&quot; I think what&#039;s meant is ones you probably don&#039;t know. Previous comments seem to suggest they think it means you would use a GUI for them instead of a command.</description>
		<content:encoded><![CDATA[<p>When the title says &#8220;10 Linux Commands You Probably Don’t Use&#8221; I think what&#8217;s meant is ones you probably don&#8217;t know. Previous comments seem to suggest they think it means you would use a GUI for them instead of a command.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zize</title>
		<link>http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/comment-page-1/#comment-17351</link>
		<dc:creator>zize</dc:creator>
		<pubDate>Sat, 31 May 2008 22:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.foogazi.com/2008/03/18/linux-commands-you-probably-dont-use/#comment-17351</guid>
		<description>I cant say i never used all these command. 
i might not use everyone every day, but it almost pisses me off all these elitist users who have to post to this blog and point out that it is a useless post because _they_ know everything about these commands so everyone else should know them. have you ever stopped to think about that the linux platform gathers new users every day, and that these users need sources to learn things?

cheers</description>
		<content:encoded><![CDATA[<p>I cant say i never used all these command.<br />
i might not use everyone every day, but it almost pisses me off all these elitist users who have to post to this blog and point out that it is a useless post because _they_ know everything about these commands so everyone else should know them. have you ever stopped to think about that the linux platform gathers new users every day, and that these users need sources to learn things?</p>
<p>cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
