|
|
i presume that when grex gets a captial letter as the first character of a login it assumes you are on a terminal that only puts out caps, and goes int a mode where it reflects all characters back as caps, and when a real cap is needed it puts a slash in front of it like /this. so every once in a while (like right now) this happens to me due to line noise or something... when this happens, how do you get it back to normal. i presume it's some sort of environment setting.
9 responses total.
Yes, when a Unix system sees upper case characters in the login id, it assumes that you're on a terminal that can only handle upper case. As far as I know, the only way to fix it is to log back out and log in again normally. One of the real Unix experts may know something that I don't, though.
This response has been erased.
Thanks, I'll try that next time.
Hmm, I thought that "stty -lcase" would *always* do it. (unless the line noise is so bad that you can't even enter the command. In which case, Plan A is indicated.)
Hmm, I'm familiar with iuclc & olcuc, but not with lcase ... but I'd have *expected* the "-" to have the reverse action of that stated. In any case, Rob's formulation of the problem is right, not the one in the initial question. The whole first line received by login has to be upper case for things to get confused. The approach is a kludge in any case (pun not intended); it has the unreasonable effect that you can't issue any commands which have any uppercase components, since *everything* gets translated. Better than no kludge at all, I guess.
Not true! If you're in upper case mode, you can send the system an "upper case" letter by putting a \ in front of it. (For this, I paid U of M countless thousands of dollars... >8)
This response has been erased.
<sigh> Rob, I should have known that ... since that's the way it differentiates upper & lower case on *output* - it shouldn't have taken much of a guess to think of that. Thanks for the correction, which may yet save my elbow some day ...
Hey, glad to help. You never know when you may *need* that information.
Response not possible - You must register and login before posting.
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss