<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<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: Saying What You Mean</title>
	<link>http://www.pythian.com/blogs/762/saying-what-you-mean</link>
	<description>News and views from Pythian DBAs</description>
	<pubDate>Mon, 12 May 2008 15:23:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Bill Karwin</title>
		<link>http://www.pythian.com/blogs/762/saying-what-you-mean#comment-172691</link>
		<dc:creator>Bill Karwin</dc:creator>
		<pubDate>Fri, 21 Mar 2008 17:03:18 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/762/saying-what-you-mean#comment-172691</guid>
		<description>Why are you starting another instance of the ksh shell if you know the current process is already a running ksh shell?  You can activate the vi behavior of command history editing in the current ksh shell:
$ set -o vi

Also, just because $SHELL is set to a value doesn't guarantee that it's accurate.  And ksh isn't always in /usr/bin.  It'd be a bit more reliable to test for `basename $0` = ksh.</description>
		<content:encoded><![CDATA[<p>Why are you starting another instance of the ksh shell if you know the current process is already a running ksh shell?  You can activate the vi behavior of command history editing in the current ksh shell:<br />
$ set -o vi</p>
<p>Also, just because $SHELL is set to a value doesn&#8217;t guarantee that it&#8217;s accurate.  And ksh isn&#8217;t always in /usr/bin.  It&#8217;d be a bit more reliable to test for `basename $0` = ksh.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
