<?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: # in vi. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528632#M24728</link>
    <description>Hi Greg:&lt;BR /&gt;&lt;BR /&gt;The appropriate place to set it is in the $HOME/.profile&lt;BR /&gt;&lt;BR /&gt;You will see the standard issue .profile already accomodates 'stty' commands.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Tue, 15 May 2001 15:12:05 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2001-05-15T15:12:05Z</dc:date>
    <item>
      <title># in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528622#M24718</link>
      <description>I have a weird one. This just started for me. When I vi a file and try to put a # in the file, it wont let me. Any ideas?</description>
      <pubDate>Tue, 15 May 2001 14:27:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528622#M24718</guid>
      <dc:creator>Greg Conn</dc:creator>
      <dc:date>2001-05-15T14:27:44Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528623#M24719</link>
      <description>What do you mean it won't let you? when you put the # does it give you an immediate response? Do you have your caps on?</description>
      <pubDate>Tue, 15 May 2001 14:33:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528623#M24719</guid>
      <dc:creator>Jim Moffitt_1</dc:creator>
      <dc:date>2001-05-15T14:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528624#M24720</link>
      <description>Greg,&lt;BR /&gt;&lt;BR /&gt;I would double check that your TERM environment variable is set correctly.  I have never seen this before, but if it happened to me, that's what I would check.  Also, verify that those keys (Shift, 3) on your keyboard work.&lt;BR /&gt;&lt;BR /&gt;I apologize if I am stating the obvious.&lt;BR /&gt;&lt;BR /&gt;-Rob</description>
      <pubDate>Tue, 15 May 2001 14:34:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528624#M24720</guid>
      <dc:creator>Robert Hoey</dc:creator>
      <dc:date>2001-05-15T14:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528625#M24721</link>
      <description>&lt;BR /&gt;Things to try;&lt;BR /&gt;&lt;BR /&gt;1. use another terminal window to vi the file. Sometimes terminal windows do crazy things and need a restart.&lt;BR /&gt;&lt;BR /&gt;2. Can you insert a # manually but doing; &lt;BR /&gt;echo \\043 &amp;gt;&amp;gt; &lt;FILENAME&gt; then vi the file and you can see the # character ? then you can move it.&lt;BR /&gt;&lt;BR /&gt;3. Check your keyboard mapping and terminal setup.&lt;/FILENAME&gt;</description>
      <pubDate>Tue, 15 May 2001 14:39:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528625#M24721</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2001-05-15T14:39:21Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528626#M24722</link>
      <description>Hi Greg, Dollars to donuts you have set the 'erase' key to '#'. That is leftover from the very old days of unix when rather than entering a backspace you enter a '#' to erase (strikeout) the character.&lt;BR /&gt;&lt;BR /&gt;You almost certainly have an incorrect TERM setting. If the problem persists after you exit vi then you can test the problem using the 'stty' command. &lt;BR /&gt;If stty reports that erase=# then that's your problem. You should then be able to do a&lt;BR /&gt;stty erase '^H' to set erase back to a backspace.&lt;BR /&gt;&lt;BR /&gt;Regards, Clay&lt;BR /&gt;</description>
      <pubDate>Tue, 15 May 2001 14:40:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528626#M24722</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-05-15T14:40:59Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528627#M24723</link>
      <description>Check your keyboard in /etc/kbdlang</description>
      <pubDate>Tue, 15 May 2001 14:41:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528627#M24723</guid>
      <dc:creator>Vincenzo Restuccia</dc:creator>
      <dc:date>2001-05-15T14:41:31Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528628#M24724</link>
      <description>Only happens on one box. Term is set right and everything else looks good. Weird! I will switch out keyboards and see what happens. Thanks, Greg</description>
      <pubDate>Tue, 15 May 2001 14:41:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528628#M24724</guid>
      <dc:creator>Greg Conn</dc:creator>
      <dc:date>2001-05-15T14:41:58Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528629#M24725</link>
      <description>I inserted it manualy and then I reset it using stty. Great job guys!</description>
      <pubDate>Tue, 15 May 2001 14:47:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528629#M24725</guid>
      <dc:creator>Greg Conn</dc:creator>
      <dc:date>2001-05-15T14:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528630#M24726</link>
      <description>When i reset it using stty and log out and then in it did not stay. Where should I check to set it perm?</description>
      <pubDate>Tue, 15 May 2001 15:06:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528630#M24726</guid>
      <dc:creator>Greg Conn</dc:creator>
      <dc:date>2001-05-15T15:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528631#M24727</link>
      <description>You can set in your .profile.&lt;BR /&gt;</description>
      <pubDate>Tue, 15 May 2001 15:11:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528631#M24727</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-05-15T15:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528632#M24728</link>
      <description>Hi Greg:&lt;BR /&gt;&lt;BR /&gt;The appropriate place to set it is in the $HOME/.profile&lt;BR /&gt;&lt;BR /&gt;You will see the standard issue .profile already accomodates 'stty' commands.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 15 May 2001 15:12:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528632#M24728</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-05-15T15:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528633#M24729</link>
      <description>Why do I have to do this? Is there a bigger configuration problem somewhere? Putting it in the .profile did work. Thanks.</description>
      <pubDate>Tue, 15 May 2001 15:31:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528633#M24729</guid>
      <dc:creator>Greg Conn</dc:creator>
      <dc:date>2001-05-15T15:31:51Z</dc:date>
    </item>
    <item>
      <title>Re: # in vi.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528634#M24730</link>
      <description>Hi Greg&lt;BR /&gt;&lt;BR /&gt;This is not a bigger config problem . It is just a matter of the env variables . It can be possible that stty erase has been set to # in the same .proifle at the  start of the file and you are just restting it . But in no case this is a bigger config problem . Dont worry at all. &lt;BR /&gt;&lt;BR /&gt;Manoj Srivastava</description>
      <pubDate>Tue, 15 May 2001 15:57:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/in-vi/m-p/2528634#M24730</guid>
      <dc:creator>MANOJ SRIVASTAVA</dc:creator>
      <dc:date>2001-05-15T15:57:12Z</dc:date>
    </item>
  </channel>
</rss>

