<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: echo : ksh &amp;lt;==&amp;gt; bash in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422044#M71222</link>
    <description>Incidentally, why are you using \012 for a linefeed when \n does it for you?</description>
    <pubDate>Mon, 15 Nov 2004 16:26:01 GMT</pubDate>
    <dc:creator>Stuart Browne</dc:creator>
    <dc:date>2004-11-15T16:26:01Z</dc:date>
    <item>
      <title>echo : ksh &lt;==&gt; bash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422042#M71220</link>
      <description>in ksh : echo "HELLO\012\HELLO"&lt;BR /&gt;delivers :&lt;BR /&gt;HELLO&lt;BR /&gt;HELLO&lt;BR /&gt;&lt;BR /&gt;in bash it delivers&lt;BR /&gt;HELLO\012HELLO&lt;BR /&gt;&lt;BR /&gt;how can I force bsh to accept \012 as linefeed ?</description>
      <pubDate>Mon, 15 Nov 2004 07:09:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422042#M71220</guid>
      <dc:creator>Werner Ittner</dc:creator>
      <dc:date>2004-11-15T07:09:19Z</dc:date>
    </item>
    <item>
      <title>Re: echo : ksh &lt;==&gt; bash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422043#M71221</link>
      <description>Hi,&lt;BR /&gt;for bash add -e option to echo command:&lt;BR /&gt;&lt;BR /&gt;echo -e "HELLO\012HELLO"&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Nov 2004 08:20:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422043#M71221</guid>
      <dc:creator>Slawomir Gora</dc:creator>
      <dc:date>2004-11-15T08:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: echo : ksh &lt;==&gt; bash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422044#M71222</link>
      <description>Incidentally, why are you using \012 for a linefeed when \n does it for you?</description>
      <pubDate>Mon, 15 Nov 2004 16:26:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422044#M71222</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-11-15T16:26:01Z</dc:date>
    </item>
    <item>
      <title>Re: echo : ksh &lt;==&gt; bash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422045#M71223</link>
      <description>And why a "\" before the second H ? :)&lt;BR /&gt;&lt;BR /&gt;Probably a porting issue, isn't it ?&lt;BR /&gt;&lt;BR /&gt;Solution is either -e option (evaluates \ codes) or replacing \012 with \n... \n would be more bash, more linux.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Fred&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Nov 2004 17:07:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/echo-ksh-lt-gt-bash/m-p/3422045#M71223</guid>
      <dc:creator>Fred Ruffet</dc:creator>
      <dc:date>2004-11-15T17:07:31Z</dc:date>
    </item>
  </channel>
</rss>

