Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Unix tcsh shell behavior question


  • Please log in to reply

#1
dfb500

dfb500

    Member

  • Member
  • PipPip
  • 75 posts
We recently moved one of our applications to a new HA supported box, we are running AIX. When using the shell window for the new box I notice some peculiarities that didn't exist on the old box. By the way, I notice this using the tcsh shell.

The first has to do with the history substitution, when using the up and down arrows to retrieve history events sometimes the event is added to the command line on top of the previous command causing gobbley gook to appear on the command line. For instance, if I entered the three commands recently of pwd, ls, less file then use the arrorws I might see the command line list less fiwd The wd gets appended to the command line and the backspace key cannot always erase the line. Hope I am explaning this right. This happens some of the time but not all of the time but enought to make history substitution problematic.

The other thing I noticed which may be related is if I less, more a large file the file contents display 1 line beyond the command line making entering more commands a problem. It appears the shell behavior is the issue but I have no idea where to start, any ideas?
  • 0

Advertisements


#2
dfb500

dfb500

    Member

  • Topic Starter
  • Member
  • PipPip
  • 75 posts
Found the answer to this myself, for all who are interested. The TERM variable was not being set properly to vt100. I added this parameter to the .profile and .cshrc file to voila, no more display issues.
  • 0

#3
admin

admin

    Founder Geek

  • Administrator
  • 24,504 posts
I think that may have been a little too geeky -- even for us. :tazz:

Thank for sharing your resolution. ;)
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP