X-Spam-Check-By: sourceware.org
Message-ID: <f894c8ac0602061101x345ae584k579735ea70db8473@mail.gmail.com>
Date: Mon, 6 Feb 2006 13:01:10 -0600
From: Zach Gelnett <zachg99 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Issue, most possibly with new Readline
In-Reply-To: <f894c8ac0602060805r553957c4h486041d19f18063c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
References: <020620061506 DOT 20451 DOT 43E765E6000A9CB000004FE322007507840A050E040D0C079D0A AT comcast DOT net> 	 <f894c8ac0602060805r553957c4h486041d19f18063c AT mail DOT gmail DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id k16J1HUT006944

On 2/6/06, Zach Gelnett <zachg99 AT XXXXXXXXX> wrote:> On 2/6/06, Eric Blake <ericblake AT XXXXXXXXX> wrote:> > > 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/> >> >>> Eric,>> Basically, when using VI as the command line editor the [ESC] puts the> line into command mode (just like pressing [ESC] within VI) then the /> says search (again it's the same command within VI) for whatever you> type next.  So, "/ls" would return the latest command line that> included the letters "ls" and i can then press "n" to get the next> occurrence and "N" to move the opposite direction through the history,> it's quite handy.>> Here is my PS1:>>  echo $PS1> \[\e]61;\u@\H\007\]\u@\H \W>>> Here is my .inputrc (i've tried commenting out the whole thing,> commenting out sections and uncommenting sections, nothing seems to> make a difference except emacs/vi):>> # the following line is actually> # equivalent to "\C-?": delete-char> "\e[3~": delete-char>> # VT> #"\e[1~": beginning-of-line> #"\e[4~": end-of-line>> # kvt> #"\e[H": beginning-of-line> #"\e[F": end-of-line>> # rxvt and konsole (i.e. the KDE-app...)> "\e[7~": beginning-of-line> "\e[8~": end-of-line> "\eOc": forward-word> "\eOd": backward-word>> # VT220> #"\eOH": beginning-of-line> #"\eOF": end-of-line>> set keymap vi> set editing-mode vi>> # Allow 8-bit input/output> set meta-flag on> set convert-meta off> set input-meta on> set output-meta on> $if Bash>   # Don't ring bell on completion>   set bell-style none>   # or, don't beep at me - show me>   set bell-style visible>   # Filename completion/expansion>   set completion-ignore-case on>   set show-all-if-ambiguous on>   # Expand homedir name>   set expand-tilde on>   # Append "/" to all dirnames>   set mark-directories on>   set mark-symlinked-directories on>   # Match all files>   set match-hidden-files on> $endif>Eric,
I like the two line format and I dont have the issue there so I thinki'll just move over and use a multi line format instead.
Thank you,Zach