<?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 dtterm and LINES setting in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dtterm-and-lines-setting/m-p/3452881#M852671</link>
    <description>When I start a dtterm using the geometry option against the local machine, LINES is set correctly, i.e. if I run:&lt;BR /&gt;&lt;BR /&gt;dtterm -display $DISPLAY -geometry 96x12+98+98&lt;BR /&gt;&lt;BR /&gt;LINES is set to 12 in the new dtterm.&lt;BR /&gt;&lt;BR /&gt;If I run the same command under remsh, then the LINES setting sometimes gets messed up, e.g. if I run&lt;BR /&gt;&lt;BR /&gt;remsh remotehost dtterm -display $DISPLAY -geometry 96x12+98+98&lt;BR /&gt;&lt;BR /&gt;LINES might come out at 13.&lt;BR /&gt;&lt;BR /&gt;Why is that?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 30 Dec 2004 10:55:18 GMT</pubDate>
    <dc:creator>Dave Burton_5</dc:creator>
    <dc:date>2004-12-30T10:55:18Z</dc:date>
    <item>
      <title>dtterm and LINES setting</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dtterm-and-lines-setting/m-p/3452881#M852671</link>
      <description>When I start a dtterm using the geometry option against the local machine, LINES is set correctly, i.e. if I run:&lt;BR /&gt;&lt;BR /&gt;dtterm -display $DISPLAY -geometry 96x12+98+98&lt;BR /&gt;&lt;BR /&gt;LINES is set to 12 in the new dtterm.&lt;BR /&gt;&lt;BR /&gt;If I run the same command under remsh, then the LINES setting sometimes gets messed up, e.g. if I run&lt;BR /&gt;&lt;BR /&gt;remsh remotehost dtterm -display $DISPLAY -geometry 96x12+98+98&lt;BR /&gt;&lt;BR /&gt;LINES might come out at 13.&lt;BR /&gt;&lt;BR /&gt;Why is that?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Dec 2004 10:55:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dtterm-and-lines-setting/m-p/3452881#M852671</guid>
      <dc:creator>Dave Burton_5</dc:creator>
      <dc:date>2004-12-30T10:55:18Z</dc:date>
    </item>
    <item>
      <title>Re: dtterm and LINES setting</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dtterm-and-lines-setting/m-p/3452882#M852672</link>
      <description>remsh is a very different network protocol. It is not telnet without a password. Indeed, remsh is really awful with interactive processes. When you start dtterm with a specific geometry, it sets the terminal's emulation size. Then a telnet connection will negotiate about window size (NAWS in telnet terminolgy, see &lt;A href="http://www.faqs.org/rfcs/rfc1073.html)." target="_blank"&gt;http://www.faqs.org/rfcs/rfc1073.html).&lt;/A&gt;&lt;BR /&gt; &lt;BR /&gt;Changing the dtterm window size generates a SIGWINCH sondition (Window Size change) and the remote telnet destination will be notified of the new values and set LINES and COLUMNS automatically. &lt;BR /&gt; &lt;BR /&gt;remsh does not do any of this type of protocol, thus the problem. You can avoid this problem by running resize or ttytype. Either program will query the terminal (dtterm) as to the current settings and generate the shell commands to change the settings. Use either one like this:&lt;BR /&gt; &lt;BR /&gt;eval $(resize)&lt;BR /&gt;or&lt;BR /&gt;eval $(ttytype -a)&lt;BR /&gt; &lt;BR /&gt;To see what they actually do, just type resize or ttytype -a. For a remsh connection, you'll have to do this every time you change the window size.</description>
      <pubDate>Thu, 30 Dec 2004 22:56:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dtterm-and-lines-setting/m-p/3452882#M852672</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2004-12-30T22:56:28Z</dc:date>
    </item>
  </channel>
</rss>

