Re: LUG: Help me spot the problem with PS1 definition - Sun, 18 Apr 2010 16:43:53 -0400

Subject : Re: LUG: Help me spot the problem with PS1 definition

From : "Daniel Underwood" <daniel.underwood@ncsu.[redacted]>

Date : Sun, 18 Apr 2010 16:43:53 -0400

Here's an example. This example is not the most bothersome or
extraordinary of examples, but it's symptomatic of the problem here at
issue. Read the explanation below and refer to the attached screenshots
when necessary.

I typed text at the command prompt, but when I attempted to enter the
"o" immediately following the "S", the cursor jumped backwards and
replaced the "D" with the "o". See screenshot 1.

Here's what the text *should* be:

ThisIsTextThatITypeButDoNotRunSo

Here's what the text *actually* shows-up as:

ThisIsTextThatITypeButooNotRunS

However, when I hit "enter" after the incorrectly displayed text, I see
that the correct text was actually passed. See screenshot 2.

Now, for comparison and as a sanity check, I tried this with a simpler
PS1 definition (which I know to be correct), and things worked
perfectly. (Refer to screenshot 2 again.)

Like I said, this example isn't really the best I could offer, it's
simply an example that I knew how to reproduce.
--
Daniel Underwood
North Carolina State University
Graduate Student - Operations Research
email: daniel.underwood@ncsu.[redacted]
phone: XXX.302.3291
web: http://www4.ncsu.edu/~djunderw/

Attachments :

(Please be wary of attachments - they have not been scanned for viruses)

Replies :

Re: LUG: Help me spot the problem with PS1 definition