John Lewis:
My apologies for
the new e-mail, I have subscribed to the mail list so that I can reply
properly in the future.
Great, much better without the privacy guff.
This is a fresh install, with no modifications (I haven't even run
mkpasswd
yet).
I start bash with the desktop icon created during the installation, the
bat
file has not been modified, it does a cd to the \bin then "bash --login
-i".
The .bashrc files are untouched and contain only comments.
Bash is definitely Cygwin version, I have no other. I mentioned less
and vim
only to show the scope of the problem, I expect they'll work correctly
once
the backspace issue is fixed.
Here is my PS1 prompt:
\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$
I tried changing the PS1 prompt to 'x' but this didn't change the
behaviour.
I've run "cygcheck -k", all keystrokes are seen and seem to have correct
values (backspace gives VK:0x08 VS: 0x0e A: 0x08)
and also "cygcheck -s -v -r", see attached.
Thanks. I can't spot anything wrong there. Could you also post the
output of 'stty -a'?
Another thing to try: install the 'mintty' terminal (by rerunning
setup.exe and selecting it in the 'Shells' category) and run it from
the entry created in the Cygwin start menu folder. That might show
whether it's an issue with bash or the console.
I think this is a clue. I did this: "cat - > fred". The keyboard
functions
correctly.
! !
O
Backspace works, ctrl-U clears the line, no erased characters are in the
file. Even the up arrow moves the cursor up a line. When used without
redirection the echoed lines are correct.
Does it still misbehave in bash after the cat?
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple