This is the mail archive of the
mailing list for the Cygwin project.
Re: CD v1.0 : 2 probs, bash readline and info
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: CD v1.0 : 2 probs, bash readline and info
- From: John Buffington <jbuff at pacific dot net>
- Date: Tue, 26 Oct 1999 11:47:36 -0700
At 10:51 PM 10/25/99 -0500, you wrote:
>I replaced my previous unstable cobbled together attempt at a
>Cygwin environment with the installation from my new copy of
>the Cygwin CD (v1.0).
>In no time at all, I ran into two problems, both of which I've already
>reported to Cygwin-Support. I've received a non-resolution type
>response to the 'info' question, but none to the readline problem,
>so far. I thought I'd see if anyone reading this list might have any
>A. "info info" and "info diff" don't work, both yield a directory page
> which doesn't contain entries for these docs. The long forms
> "info -f /usr/info/info" and "info -f /usr/info/diff" do work properly.
> "export INFOPATH="/usr/info:/contrib/info" doesn't help.
>B. I ran across two problems with text entry into the bash shell.
> I use "set -o vi" and a simple ".inputrc":
> # Make Bash 8bit clean
> set meta-flag on
> set convert-meta off
> set output-meta on
> # Ignore case while completing
> set completion-ignore-case on
> At first, I couldn't enter an 's', though I did discover that ctrl-v-s
> worked. After turning off the "set -o vi" (reverting to emacs) and
> commenting-out the .inputrc entries, the 's' was accepted and
> then after putting the .inputrc back the way it was and going
> back to the "set -o vi" the 's' continued to work okay - so much
> for diagnosing that problem!
I had (still have) a similar problem with the cygwin CD and W98
mine would not accept an 'e'. I finally renamed my .inputrc file
to make the problem go away while I did other things. So far the
lack of an .inputrc file hasn't hurt me, but I'd like to know what's going on.
"No matter where you go, there you are." ......... Buckaroo Banzai
Want to unsubscribe from this list?
Send a message to email@example.com