X-Spam-Check-By: sourceware.org
From: ericblake AT comcast DOT net (Eric Blake)
To: Zach Gelnett <zachg99 AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Issue, most possibly with new Readline
Date: Mon, 06 Feb 2006 15:06:14 +0000
Message-Id: <020620061506.20451.43E765E6000A9CB000004FE322007507840A050E040D0C079D0A@comcast.net>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

> After installing the latest readline updates (that fixed the earlier
> prompt issue) I'm finding an issue with the vi command line interface.
> 
> Basically, when I hit [ESC] then fwd slash (/) to search through the
> history, it throws my cursor back to get beginning of the line (on top
> of the prompt) and acts weird.  This is in mrxvt, now if I do the same
> in the basic cygwin bash shell i get this:
> 
> v468929 AT TRD-CAX40JXD ~> / 
> ☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺

I could not reproduce this with a quick check (I normally
use set -o emacs, so I am practically clueless about
vi mode).  Also, I normally use a multiline prompt, which
may be impacting things.  I tried:

$ echo $PS1
\[\e]0;\w\a\e[0m\]\n\[\e[32m\]\u@\h \ \[\e[35m\](${PIPESTATUS[*]}) \[\e[33m\]~\[\e[0m\]\n\$
eblake AT eblake (0) ~
$ echo hi
hi
eblake AT eblake (0) ~
$ [ESC]/e[ENTER]       # those four keystrokes rewrite this line as:
$ echo hi         # with the cursor on the e


What is your PS1?  What settings do you have in your ~/.inputrc?

One other thing to be aware of - readline 5.1 official patch 2
was released this weekend, so I need to make a 5.1-3 cygwin
release soon to incorporate it (it dealt with initialization issues
with line-wrapping).  I don't know if your bug would have been
fixed by official patch 2, or whether I should spend more time
investigating this first.

--
Eric Blake
volunteer cygwin readline maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/