From: Chris Faylor <cygwin@sourceware.cygnus.com>
To: 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: <19990822183809.B1175@cygnus.com> (raw)
Message-ID: <19990831234900.aMBIdukihpEurq--8ZGQZ_tLsOKg15tgsRjYHs97h1Y@z> (raw)
In-Reply-To: <37C0678A.E9F373E5@vinschen.de>
On Sun, Aug 22, 1999 at 11:11:38PM +0200, Corinna Vinschen wrote:
>But there are more problems with keystrokes that are not specific to
>cygwin but are nevertheless disturbing. Example vi: When I learnt
>using vi, I learnt three commands which are very convenient:
>
> Ctrl + 6 change to alternative file
> Ctrl + ^ ditto
> Ctrl + ] goto tag under cursor
>
>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
>keyboard the circumflex is a dead key for national characters (though
>not existing in german language), the brackets are only reached by
>using the right Alt key (Alt Gr).
Ok. This one I understand. There would probably be no problem adding
this functionality.
>Conclusion: The cursor problem of 9X and special key handlings
>on native keyboards will result in problems for all times.
>I would be glad, if there would be a solution to make a special key
>mapping in cygwin that is independent of [no]tty setting and used OS.
>This could be e.g. a .cygkey file in the home directory or something
>comparable.
>IMHO, this should be addressed in the future (b22).
Yep. We could have some kind of capability which allowed you to define
keys, similar to linux.
That's definitely B22 functionality.
-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 [this message]
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
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=19990822183809.B1175@cygnus.com \
--to=cygwin@sourceware.cygnus.com \
/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).