<?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: ksh shell print command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515178#M889125</link>
    <description>The easiest way around this is to invoke the command with the full path (same as the which command output).  I know its extra typing but this method takes things like PATH variables and shell internal mechanisms out of the picture.</description>
    <pubDate>Mon, 09 Apr 2001 19:44:55 GMT</pubDate>
    <dc:creator>Tim Malnati</dc:creator>
    <dc:date>2001-04-09T19:44:55Z</dc:date>
    <item>
      <title>ksh shell print command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515173#M889120</link>
      <description>I have installed a xerox printing software that insatlled a command called "print". It is set in my PATH. The command is found when I do a "which print". But when I try to execute it the shell command "print" takes precedence over the installed xerox "print" command. Is there away around this?</description>
      <pubDate>Mon, 09 Apr 2001 14:29:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515173#M889120</guid>
      <dc:creator>Joseph Hoh</dc:creator>
      <dc:date>2001-04-09T14:29:16Z</dc:date>
    </item>
    <item>
      <title>Re: ksh shell print command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515174#M889121</link>
      <description>Hi Jeff:&lt;BR /&gt;&lt;BR /&gt;I'd define an alias for the "print" in you profile that points to the full path executable:&lt;BR /&gt;&lt;BR /&gt;# alias printx=/&lt;YOUR_EXECUTABLE&gt;&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;/YOUR_EXECUTABLE&gt;</description>
      <pubDate>Mon, 09 Apr 2001 14:44:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515174#M889121</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-04-09T14:44:46Z</dc:date>
    </item>
    <item>
      <title>Re: ksh shell print command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515175#M889122</link>
      <description>For printing use lp.</description>
      <pubDate>Mon, 09 Apr 2001 14:47:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515175#M889122</guid>
      <dc:creator>Vincenzo Restuccia</dc:creator>
      <dc:date>2001-04-09T14:47:58Z</dc:date>
    </item>
    <item>
      <title>Re: ksh shell print command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515176#M889123</link>
      <description>Would it work if you tried executing the print command using the full pathname?</description>
      <pubDate>Mon, 09 Apr 2001 15:26:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515176#M889123</guid>
      <dc:creator>Tracey</dc:creator>
      <dc:date>2001-04-09T15:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: ksh shell print command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515177#M889124</link>
      <description>Since print is a special command ( built in command ) for the shell , the shell will try and execute the special command ( in the current shell process ) before searching the PATH variable. The "which" command output has verified that you have set up your PATH correctly to use the Xerox executable. After this, the following should work .&lt;BR /&gt;&lt;BR /&gt;# ksh print  &lt;BR /&gt;   or&lt;BR /&gt;# sh print &lt;BR /&gt;&lt;BR /&gt;This will force the search through your PATH Variable.</description>
      <pubDate>Mon, 09 Apr 2001 19:04:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515177#M889124</guid>
      <dc:creator>AstraZeneca Unix Staff</dc:creator>
      <dc:date>2001-04-09T19:04:51Z</dc:date>
    </item>
    <item>
      <title>Re: ksh shell print command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515178#M889125</link>
      <description>The easiest way around this is to invoke the command with the full path (same as the which command output).  I know its extra typing but this method takes things like PATH variables and shell internal mechanisms out of the picture.</description>
      <pubDate>Mon, 09 Apr 2001 19:44:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-shell-print-command/m-p/2515178#M889125</guid>
      <dc:creator>Tim Malnati</dc:creator>
      <dc:date>2001-04-09T19:44:55Z</dc:date>
    </item>
  </channel>
</rss>

