From: Chris Faylor <cygwin@sourceware.cygnus.com>
To: Corinna Vinschen <corinna@vinschen.de>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Cursors do not work in bash under Win98
Date: Tue, 31 Aug 1999 23:49:00 -0000 [thread overview]
Message-ID: <19990823105008.A13734@cygnus.com> (raw)
Message-ID: <19990831234900.kVdA6QQHQbWHtG209oxQOe5-qc7cv1xqat-cBc9d5Ag@z> (raw)
In-Reply-To: <37C11145.AA5E23E5@vinschen.de>
On Mon, Aug 23, 1999 at 11:15:49AM +0200, Corinna Vinschen wrote:
>Chris Faylor wrote:
>> >On Sun, Aug 22, 1999 at 11:11:38PM +0200, Corinna Vinschen wrote:
>> >[...]
>> >>All commands never worked with a vi under cygwin. AFAIK this is a
>> >>problem of native keyboards under win32. The key combinations
>> >>doesn't unfortunately generate any ascii characters. On the german
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Remember this...
>
>> Actually, I just tried ctrl-6 and ctrl-] and both "work form me".
>
>Congratulations!
>Maybe you are using an american keyboard? ;)
Ah. Yes. The fact that I was using an American keyboard was kinda what
started this. Remember?
>BTW: When I use american keyboard layout with my german keyboard the
>ctrl-] works but ctrl-6 and ctrl-^ (Ahhh, I see, it's the same key on
>american keyboards... now I remember again...) still doesn't work.
>
>Glenn Spell wrote:
>> What program are you using as 'vi'?
>
>Good question. I'm using vim 5.3, cygwin w/o gui build by Michael
I'm using vim 5.0, built by me.
-chris
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-08-31 23:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 20:38 Nuno Bandeira
1999-08-19 17:15 ` Michael Weiser
1999-08-20 3:05 ` Re[2]: " Paul Sokolovsky
1999-08-20 14:29 ` Michael Weiser
1999-08-20 14:45 ` Chris Faylor
1999-08-21 13:28 ` Michael Weiser
1999-08-21 19:08 ` Chris Faylor
1999-08-25 13:31 ` Michael Weiser
1999-08-31 23:49 ` Michael Weiser
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Michael Weiser
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Michael Weiser
1999-08-21 10:28 ` Nuno Bandeira
1999-08-21 11:49 ` Re[2]: " Paul Sokolovsky
1999-08-22 8:39 ` Nuno Bandeira
1999-08-22 10:36 ` Chris Faylor
[not found] ` <37C0678A.E9F373E5@vinschen.de>
1999-08-22 15:36 ` Chris Faylor
1999-08-22 15:39 ` Chris Faylor
1999-08-22 20:15 ` Glenn Spell
1999-08-31 23:49 ` Glenn Spell
1999-08-23 2:32 ` Corinna Vinschen
1999-08-23 5:35 ` Nuno Bandeira
1999-08-23 7:10 ` Corinna Vinschen
1999-08-31 23:49 ` Corinna Vinschen
1999-08-31 23:49 ` Nuno Bandeira
1999-08-23 7:48 ` Chris Faylor [this message]
1999-08-26 3:56 ` Corinna Vinschen
1999-08-31 23:49 ` Corinna Vinschen
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Corinna Vinschen
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Chris Faylor
1999-08-23 2:32 ` Corinna Vinschen
1999-08-31 23:49 ` Corinna Vinschen
1999-08-31 23:49 ` Chris Faylor
1999-08-31 23:49 ` Nuno Bandeira
1999-08-31 23:49 ` Re[2]: " Paul Sokolovsky
1999-08-31 23:49 ` Nuno Bandeira
1999-08-31 23:49 ` Re[2]: " Paul Sokolovsky
1999-08-31 23:49 ` Michael Weiser
1999-08-31 23:49 ` Nuno Bandeira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990823105008.A13734@cygnus.com \
--to=cygwin@sourceware.cygnus.com \
--cc=corinna@vinschen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).