<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Use multiple tabs in Linux or OS X without losing your history</title>
	<link>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Thu, 28 Aug 2008 11:55:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Robert Goldman</title>
		<link>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2737</link>
		<dc:creator>Robert Goldman</dc:creator>
		<pubDate>Fri, 16 Nov 2007 17:19:04 +0000</pubDate>
		<guid>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2737</guid>
		<description>One thing that might be even better would be to be able to save *separate* histories for multiple shells.  I typically have as many as 8 different terminal windows open at once.  I think it would be great to have separate histories and, even more, separate directory stacks (I use pushd and popd a lot) for each of the terminal windows.  Somehow, though, you'd have to be able to have a terminal window "know" its identity, and then when restarted (I use KDE) somehow find the same identity.  If you could do that, it would be simple to associate separate histories and directory stacks with separate shell instances.</description>
		<content:encoded><![CDATA[<p>One thing that might be even better would be to be able to save *separate* histories for multiple shells.  I typically have as many as 8 different terminal windows open at once.  I think it would be great to have separate histories and, even more, separate directory stacks (I use pushd and popd a lot) for each of the terminal windows.  Somehow, though, you&#8217;d have to be able to have a terminal window &#8220;know&#8221; its identity, and then when restarted (I use KDE) somehow find the same identity.  If you could do that, it would be simple to associate separate histories and directory stacks with separate shell instances.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thinux</title>
		<link>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2736</link>
		<dc:creator>thinux</dc:creator>
		<pubDate>Sun, 11 Nov 2007 03:00:27 +0000</pubDate>
		<guid>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2736</guid>
		<description>great, i am annoyed by this problem for a long time.</description>
		<content:encoded><![CDATA[<p>great, i am annoyed by this problem for a long time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin McCallion</title>
		<link>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2735</link>
		<dc:creator>Martin McCallion</dc:creator>
		<pubDate>Thu, 08 Nov 2007 15:56:53 +0000</pubDate>
		<guid>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2735</guid>
		<description>Excellent!  You might be interested to know that it also works in Cygwin Bash (not surprisingly).</description>
		<content:encoded><![CDATA[<p>Excellent!  You might be interested to know that it also works in Cygwin Bash (not surprisingly).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mightybs</title>
		<link>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2734</link>
		<dc:creator>mightybs</dc:creator>
		<pubDate>Thu, 08 Nov 2007 07:58:50 +0000</pubDate>
		<guid>http://venturecake.com/use-multiple-tabs-in-linux-or-os-x-without-losing-your-history/#comment-2734</guid>
		<description>&lt;p&gt;For anyone wanting to keep any default, or previously defined PROMPT_COMMAND you'd want to use something like this:&lt;/p&gt;
&lt;p&gt;PROMPT_COMMAND="${PROMPT_COMMAND}; history -a;"&lt;/p&gt;
&lt;p&gt;This way you can keep the previously set PROMPT_COMMAND, by redefining PROMPT_COMMAND with itself and adding on your desired commands.&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Ed:&lt;/strong&gt;Great suggestion Brett - I've added it to the article. Thanks!&lt;/em&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>For anyone wanting to keep any default, or previously defined PROMPT_COMMAND you&#8217;d want to use something like this:</p>
<p>PROMPT_COMMAND=&#8221;${PROMPT_COMMAND}; history -a;&#8221;</p>
<p>This way you can keep the previously set PROMPT_COMMAND, by redefining PROMPT_COMMAND with itself and adding on your desired commands.</p>
<p><em><strong>Ed:</strong>Great suggestion Brett - I&#8217;ve added it to the article. Thanks!</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>
