<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<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: From bash to ksh&#8230;</title>
	<link>http://www.michael-clarke-blog.com/2008/04/13/from-bash-to-ksh/</link>
	<description>Me, Operating Systems, Technology, Sun Microsystems and Stuff!</description>
	<pubDate>Thu, 21 Aug 2008 07:30:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Michael Clarke</title>
		<link>http://www.michael-clarke-blog.com/2008/04/13/from-bash-to-ksh/#comment-66</link>
		<dc:creator>Michael Clarke</dc:creator>
		<pubDate>Sun, 13 Apr 2008 18:57:26 +0000</pubDate>
		<guid>http://www.michael-clarke-blog.com/2008/04/13/from-bash-to-ksh/#comment-66</guid>
		<description>Lewis -

I did look at zsh - but I didn't like the stupid welcome thing it gave me the first time I typed 'zsh' and all this menu to set it up etc. Besides, I don't see the difference really between zsh, bash, ksh etc as I put the thing straight into vi mode anyway and then use vi functionality for navigating around, completion (Esc + \ and Esc + =) etc etc.... In essence they're all the same - just one displays correctly and the other simply doesn't!

In regards to the 'fix' - it's more of a work around. If ksh doesn't suffer the problem why does bash? The developers of Korn Shell evidently found a way to get around it - why didn't the developers of bash? Maybe I'll write a patch if I can find the time, but at the moment my dtrace bug and MouthOS is taking most of my spare time ;)



Jerry -

Indeed I quite agree. I'm finding it so much nicer not having all these detractions on my desktop when I'm working :)


Mike</description>
		<content:encoded><![CDATA[<p>Lewis -</p>
<p>I did look at zsh - but I didn&#8217;t like the stupid welcome thing it gave me the first time I typed &#8216;zsh&#8217; and all this menu to set it up etc. Besides, I don&#8217;t see the difference really between zsh, bash, ksh etc as I put the thing straight into vi mode anyway and then use vi functionality for navigating around, completion (Esc + \ and Esc + =) etc etc&#8230;. In essence they&#8217;re all the same - just one displays correctly and the other simply doesn&#8217;t!</p>
<p>In regards to the &#8216;fix&#8217; - it&#8217;s more of a work around. If ksh doesn&#8217;t suffer the problem why does bash? The developers of Korn Shell evidently found a way to get around it - why didn&#8217;t the developers of bash? Maybe I&#8217;ll write a patch if I can find the time, but at the moment my dtrace bug and MouthOS is taking most of my spare time <img src='http://www.michael-clarke-blog.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Jerry -</p>
<p>Indeed I quite agree. I&#8217;m finding it so much nicer not having all these detractions on my desktop when I&#8217;m working <img src='http://www.michael-clarke-blog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry Rocteur</title>
		<link>http://www.michael-clarke-blog.com/2008/04/13/from-bash-to-ksh/#comment-65</link>
		<dc:creator>Jerry Rocteur</dc:creator>
		<pubDate>Sun, 13 Apr 2008 17:06:25 +0000</pubDate>
		<guid>http://www.michael-clarke-blog.com/2008/04/13/from-bash-to-ksh/#comment-65</guid>
		<description>I think this is a normal transition when you really want to be productive. Next you'll move from fvwm2 to ion3 !!

You'll also not care too much about colour except perhaps in syntax highlighting in vim 

This is good news, I wish more people would be less interested in GUIs and more in getting the job done!</description>
		<content:encoded><![CDATA[<p>I think this is a normal transition when you really want to be productive. Next you&#8217;ll move from fvwm2 to ion3 !!</p>
<p>You&#8217;ll also not care too much about colour except perhaps in syntax highlighting in vim </p>
<p>This is good news, I wish more people would be less interested in GUIs and more in getting the job done!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lewis</title>
		<link>http://www.michael-clarke-blog.com/2008/04/13/from-bash-to-ksh/#comment-64</link>
		<dc:creator>Lewis</dc:creator>
		<pubDate>Sun, 13 Apr 2008 13:28:00 +0000</pubDate>
		<guid>http://www.michael-clarke-blog.com/2008/04/13/from-bash-to-ksh/#comment-64</guid>
		<description>On the whole I'd say that ksh is a lost cause
I'm considering a move to zsh... it all comes down to how powerful zsh's programmable tab completion is

As to why bash messes up... it's because the terminal was resized while a process was running, i.e. bash didn't get the signal to notify it that the rows/columns had changed.  You can fix it by re-resizing the window</description>
		<content:encoded><![CDATA[<p>On the whole I&#8217;d say that ksh is a lost cause<br />
I&#8217;m considering a move to zsh&#8230; it all comes down to how powerful zsh&#8217;s programmable tab completion is</p>
<p>As to why bash messes up&#8230; it&#8217;s because the terminal was resized while a process was running, i.e. bash didn&#8217;t get the signal to notify it that the rows/columns had changed.  You can fix it by re-resizing the window</p>
]]></content:encoded>
	</item>
</channel>
</rss>
