<?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: How to decide TERM value in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-decide-term-value/m-p/3047583#M135769</link>
    <description>Hi Ezhil,&lt;BR /&gt;&lt;BR /&gt;It sometimes depends on the unix box you use. Mostly with all Unix flavors vt100 works just fine. You don't have to set it every time but you can put the same in your .profile.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Karthik S S</description>
    <pubDate>Wed, 13 Aug 2003 00:04:55 GMT</pubDate>
    <dc:creator>Karthik S S</dc:creator>
    <dc:date>2003-08-13T00:04:55Z</dc:date>
    <item>
      <title>How to decide TERM value</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-decide-term-value/m-p/3047582#M135768</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;   I do not have clear idea in setting TERM value. We are using different software ( telnet, Crt, Tnvt, ..) to connect to many Unix m/c. If vi ( editing file ) is not OK, we change TERM=vt100 or vt220 or hp .., it works.&lt;BR /&gt;&lt;BR /&gt;But how to decide on TERM value ?&lt;BR /&gt;does it depend on Unix m/c or software we are using to connect or depend on our PC&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;R.Ezhil&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Aug 2003 22:30:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-decide-term-value/m-p/3047582#M135768</guid>
      <dc:creator>ezhilarasan_1</dc:creator>
      <dc:date>2003-08-12T22:30:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to decide TERM value</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-decide-term-value/m-p/3047583#M135769</link>
      <description>Hi Ezhil,&lt;BR /&gt;&lt;BR /&gt;It sometimes depends on the unix box you use. Mostly with all Unix flavors vt100 works just fine. You don't have to set it every time but you can put the same in your .profile.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Karthik S S</description>
      <pubDate>Wed, 13 Aug 2003 00:04:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-decide-term-value/m-p/3047583#M135769</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2003-08-13T00:04:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to decide TERM value</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-decide-term-value/m-p/3047584#M135770</link>
      <description>It is best NEVER to hardcode the TERM value in /etc/profile and/or .profile since there may are dozens of different terminals (and emulators) that might be used. Hardcoding TERM means that some users will be OK and others will not. HP-UX has a program that identifies terminals (and emulators) automatically: ttytype&lt;BR /&gt;&lt;BR /&gt;However, the standard /etc/profile will bypass this invaluable tool by testing whether TERM has been set before /etc/profile starts. This is a problem since telnet has a subcode that some opsystems will pass through to HP-UX and may not be useful for HP-UX. So, eliminate the test in /etc/profile to see if TERM has been set:&lt;BR /&gt;&lt;BR /&gt;if [ "$TERM" = "" -o "$TERM" = "unknown" -o "$TERM" = "dialup" -o "$TERM" = "network" ]&lt;BR /&gt;then&lt;BR /&gt;eval `ttytype -s -a`&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;and replace it with:&lt;BR /&gt;&lt;BR /&gt;eval $(ttytype -s)&lt;BR /&gt;&lt;BR /&gt;Now, every login will be correctly evaluated and programs like vi will work correctly.</description>
      <pubDate>Wed, 13 Aug 2003 01:44:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-decide-term-value/m-p/3047584#M135770</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-08-13T01:44:57Z</dc:date>
    </item>
  </channel>
</rss>

