<?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: diff TERM and DISPLAY in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700442#M249206</link>
    <description>hi Amit.&lt;BR /&gt;the TERM variable sets the TERMinal value.&lt;BR /&gt;most commonly used are vg100/vt220/hp&lt;BR /&gt;e.g.&lt;BR /&gt;# export TERM=vt100&lt;BR /&gt;or&lt;BR /&gt;# export TERM=hp&lt;BR /&gt;&lt;BR /&gt;The DISPLAY variable shows where graphical output must be send to...&lt;BR /&gt;most commonly it is set as an ip-adres.&lt;BR /&gt;eg. &lt;BR /&gt;# export DISPLAY=10.124.3.211:0.0&lt;BR /&gt;&lt;BR /&gt;regards.</description>
    <pubDate>Sat, 31 Dec 2005 08:23:48 GMT</pubDate>
    <dc:creator>Henk Geurts</dc:creator>
    <dc:date>2005-12-31T08:23:48Z</dc:date>
    <item>
      <title>diff TERM and DISPLAY</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700441#M249205</link>
      <description>hi all&lt;BR /&gt;can any body tell me the env variable TERM and &lt;BR /&gt;difference beetween TERM and DISPLAY.&lt;BR /&gt;thanks and regards&lt;BR /&gt;amit kumar</description>
      <pubDate>Sat, 31 Dec 2005 06:17:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700441#M249205</guid>
      <dc:creator>amit kumar_5</dc:creator>
      <dc:date>2005-12-31T06:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: diff TERM and DISPLAY</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700442#M249206</link>
      <description>hi Amit.&lt;BR /&gt;the TERM variable sets the TERMinal value.&lt;BR /&gt;most commonly used are vg100/vt220/hp&lt;BR /&gt;e.g.&lt;BR /&gt;# export TERM=vt100&lt;BR /&gt;or&lt;BR /&gt;# export TERM=hp&lt;BR /&gt;&lt;BR /&gt;The DISPLAY variable shows where graphical output must be send to...&lt;BR /&gt;most commonly it is set as an ip-adres.&lt;BR /&gt;eg. &lt;BR /&gt;# export DISPLAY=10.124.3.211:0.0&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Sat, 31 Dec 2005 08:23:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700442#M249206</guid>
      <dc:creator>Henk Geurts</dc:creator>
      <dc:date>2005-12-31T08:23:48Z</dc:date>
    </item>
    <item>
      <title>Re: diff TERM and DISPLAY</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700443#M249207</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;TERM defines behavior of an opened terminal, DISPLAY defines on what host to open terminal by X application.&lt;BR /&gt;&lt;BR /&gt;If you want to open xterm application on machine called foo, you write on your computer &lt;BR /&gt;export DISPLAY=foo:0.0&lt;BR /&gt;&lt;BR /&gt;Now, if you want to change kind of terminal behaviou, you can in the opened window define export TERM=vt100 or vt200 or whatever you need.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 31 Dec 2005 12:42:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700443#M249207</guid>
      <dc:creator>Victor Fridyev</dc:creator>
      <dc:date>2005-12-31T12:42:17Z</dc:date>
    </item>
    <item>
      <title>Re: diff TERM and DISPLAY</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700444#M249208</link>
      <description>TERM contains the name or type of your terminal.It is usually set through /etc/profile shell startup file using either the tset or ttytype command.Comand like more and vi need this variable to display files correctly on different terminals.&lt;BR /&gt;DISPLAY contains the host name or ip address of remote box that your server should use to send XF86 based application to it.</description>
      <pubDate>Sat, 31 Dec 2005 13:46:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700444#M249208</guid>
      <dc:creator>Delrish</dc:creator>
      <dc:date>2005-12-31T13:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: diff TERM and DISPLAY</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700445#M249209</link>
      <description>It is very easy to confuse the two when Xwindows (the graphics subsystem on Unix) is confused with Unix (which is a commandline-based system) terminal interfaces. The majority of Unix admins seldom work with pictures, drawings, color designs, etc, yet they will always start a window that is emulating a 'real' terminal. So the basic way to talk to the HP-UX system is using the shell command line. And the method of communication is a terminal, a glass teletype or keyboard+display.&lt;BR /&gt; &lt;BR /&gt;Now there are hundreds of terminal models, dozens of manufacturers, each with varied capabilities and standards. Now with a command line, none of these variants are important. All that is needed is a plain ASCII terminal so things like LINES and COLUMNS are unimportant. But take something extremely complicated like vi, and everything changes. vi needs to know hundreds of special features from LINES and COLUMNS to the spcial codes to move the cursor around the screen. Now all those features make the terminal differences very important. So a special library of routines called Curses was created that could accomodate all these differences. The library defines tasks which a program (like vi) needs to accomplish, and a database of character codes is consulted to produce the desired task. That's where TERM comes in Once TERM matches the terminal being used, all the correct codes will be used by the program. But manually set TERM without regard to the actual terminal (or more common, an emualtor program on a PC) and vi will be a mess on the screen.&lt;BR /&gt; &lt;BR /&gt;To simplify everything, HP-UX has a smart terminal ID program called ttytype which will query your terminal at login and set TERM correctly.&lt;BR /&gt; &lt;BR /&gt;Now DISPLAY has nothing whatsoever to do with TERM. DISPLAY is an IP address, a display identifier and a workspace and is used by Xwindows to direct all the colors and decorations and mouse/keyboard communication to a display server (the screen + keyboard + mouse). On a graphics workstation, these 3 items are self-contained, but the application program will use whatever the IP address is specified by DISPLAY.&lt;BR /&gt; &lt;BR /&gt;So where this gets confused is when you are running in an Xwindow environment and start a terminal program. The DISPLAY value simply points to the display server where the colors and text will be displayed, but the terminal program (such as dtterm, xterm or hpterm) will login and must have TERM set correctly. Unfortunately the default Xwindow environment bypasses the normal login profiles so the TERM value is often mis-set. To see if it is correctly set, once you are logged into HP-UX, type these two commands:&lt;BR /&gt; &lt;BR /&gt;ttytype -s&lt;BR /&gt;echo $TERM&lt;BR /&gt; &lt;BR /&gt;The TERM value should match and if so, your text window is ready to use.</description>
      <pubDate>Sun, 01 Jan 2006 23:02:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diff-term-and-display/m-p/3700445#M249209</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2006-01-01T23:02:11Z</dc:date>
    </item>
  </channel>
</rss>

