On Mon, 25 Nov 2002, Daniel Jarboe wrote: > For the past few weeks I've had the following occur... > > When editing documents in vi, after a :wq I won't get the shell prompt > on a new line anymore. I'll see something like: > > [dan@tcsl dan]$ 50629C written > Which is the shell prompt over the text: "test.txt" 637L, 50629C written > > This is on a RH 7.2 system, and it's not specific to my user/profile. > I'm pretty sure it didn't use to be like this, any ideas what would > cause this kind of behavior, so I can be more specific in my searching? > I'm ssh'ing in with PuTTY. clear and reset don't help. When I ran > 'screen', it worked properly, but after exiting the original problem > continued. I don't think I ever changed the prompt or anything. I'm at > a loss.
How very interesting. There's recently been some heated discussion on the Psyche (RHL 8.0) list about something related to this: [summer@orange summer]$ echo -n test my line-feed, it seems shot to bits [summer@orange summer]$ ems shot to bits In contrast, RHL 7.3: [summer@dugite summer]$ echo -n test my line-feed, it seems shot to bits test my line-feed, it seems shot to bits[summer@dugite summer]$ I don't know that it's resolved, I quit following it. It originally arose as a Perl problem, and AFAIK it's not been pointed out that the echo command can cause the problem. There may be a Bugzilla report on it. I suggest you try combinations of rpm -V to test for altered packages, rpm -qa --last to see what's been installed recently, and compare your .bashrc and .bash_profile with those in /etc/skel to see if you can find what's changed. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
