<?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: history  &#8212; a bash command</title>
	<atom:link href="http://www.accessdataservices.com/blog/bash-history-command/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.accessdataservices.com/blog/bash-history-command/</link>
	<description>Linux, Freedom, and More</description>
	<lastBuildDate>Mon, 16 Jan 2012 22:37:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: gare</title>
		<link>http://www.accessdataservices.com/blog/bash-history-command/comment-page-1/#comment-48718</link>
		<dc:creator>gare</dc:creator>
		<pubDate>Wed, 08 Dec 2010 14:18:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.accessdataservices.com/blog/bash-history-command/#comment-48718</guid>
		<description>esp. note:

executes commands from the file /etc/profile, if that file exists. 
After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile,

</description>
		<content:encoded><![CDATA[<p>esp. note:</p>
<p>executes commands from the file /etc/profile, if that file exists.<br />
After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gare</title>
		<link>http://www.accessdataservices.com/blog/bash-history-command/comment-page-1/#comment-39622</link>
		<dc:creator>gare</dc:creator>
		<pubDate>Fri, 28 Aug 2009 13:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.accessdataservices.com/blog/bash-history-command/#comment-39622</guid>
		<description>Hi -

Yes there is a way to bring a command onto the command line without executing it. There are at least  2 ways:

1. Press the up arrow key to bring up previous commands.

2. reverse search history:
     a.  ctrl-R 
     b.  then type part of the command you are looking for.
     c. ctrl-R to go to next found result
     d. End key to keep what you find on the command line.

  
Thanks for writing!
Gare</description>
		<content:encoded><![CDATA[<p>Hi -</p>
<p>Yes there is a way to bring a command onto the command line without executing it. There are at least  2 ways:</p>
<p>1. Press the up arrow key to bring up previous commands.</p>
<p>2. reverse search history:<br />
     a.  ctrl-R<br />
     b.  then type part of the command you are looking for.<br />
     c. ctrl-R to go to next found result<br />
     d. End key to keep what you find on the command line.</p>
<p>Thanks for writing!<br />
Gare</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BobbyW</title>
		<link>http://www.accessdataservices.com/blog/bash-history-command/comment-page-1/#comment-39608</link>
		<dc:creator>BobbyW</dc:creator>
		<pubDate>Thu, 27 Aug 2009 19:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.accessdataservices.com/blog/bash-history-command/#comment-39608</guid>
		<description>So close to what I need !

OT - Is there a way to populate text at the prompt so it&#039;s waiting for you to hit return or type more text and then you can hit return.   

I&#039;m looking for the functionality of something like an alias, but I want the text of the command written out at the prompt, not executed.

Thanks so much.</description>
		<content:encoded><![CDATA[<p>So close to what I need !</p>
<p>OT &#8211; Is there a way to populate text at the prompt so it&#8217;s waiting for you to hit return or type more text and then you can hit return.   </p>
<p>I&#8217;m looking for the functionality of something like an alias, but I want the text of the command written out at the prompt, not executed.</p>
<p>Thanks so much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tar -zxvf .com &#187; bash_history com data</title>
		<link>http://www.accessdataservices.com/blog/bash-history-command/comment-page-1/#comment-29146</link>
		<dc:creator>tar -zxvf .com &#187; bash_history com data</dc:creator>
		<pubDate>Thu, 11 Sep 2008 21:03:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.accessdataservices.com/blog/bash-history-command/#comment-29146</guid>
		<description>[...] HISTIGNORE=”:ls:[bf]g:exit” (detalhes aqui) # comandos que não serão adicionados ao [...]</description>
		<content:encoded><![CDATA[<p>[...] HISTIGNORE=”:ls:[bf]g:exit” (detalhes aqui) # comandos que não serão adicionados ao [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tar -zxvf .com &#187; bash_history com data</title>
		<link>http://www.accessdataservices.com/blog/bash-history-command/comment-page-1/#comment-29145</link>
		<dc:creator>tar -zxvf .com &#187; bash_history com data</dc:creator>
		<pubDate>Thu, 11 Sep 2008 21:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.accessdataservices.com/blog/bash-history-command/#comment-29145</guid>
		<description>[...] # define o arquivo history  export HISTIGNORE=”:ls:[bf]g:exit” (detalhes aqui) # comandos que não serão adicionados ao history   Tagged: [...]</description>
		<content:encoded><![CDATA[<p>[...] # define o arquivo history  export HISTIGNORE=”:ls:[bf]g:exit” (detalhes aqui) # comandos que não serão adicionados ao history   Tagged: [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

