git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin <kevin071586@yahoo.com>
To: git@vger.kernel.org
Subject: CTRL+Arrow keys don't work with Git Bash for Windows?
Date: Thu, 29 Jan 2015 15:18:26 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150129T161729-820@post.gmane.org> (raw)

Hello,
I'm trying to set up some navigation shortcuts I have become accustomed to
using in Windows environments, as well as KDE Konsole.  I would like to bind
CTRL+Left to "backward-word" and CTRL+Right to "forward-word" (there are
more, but this is a start).  I can enable this behavior by adding something
like "\e[D": forward-word to my ./inputrc file, but this also overwrites the
"forward-char" sequence that comes from a "Right Arrow" press without the
CTRL key.  For some reason, when I use the Git Bash shell the key sequence
for "CTRL+Right" and "Right" (\e[C) are the same -- same with "CTRL+Left"
and "Left" (\e[D).

Most of the solutions I have come across only address adding things to the
".inputrc" file, but in this case that is not the problem.  The problem is
that the CTRL+Arrow keys are not sending any unique sequences.  These
sequences are distinct and can be bound as I am describing when using the
"mintty.exe" xterm terminal emulator.  So why are they not working when I
start up Git Bash (which I believe has no emulator, it just uses windows
cmd.exe?).  I also see this problem when I use the "bash.exe --login -l"
that was installed with MinGW/MSys.

Thanks for any suggestions on how to enable this behavior.

Kevin

             reply	other threads:[~2015-01-29 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 15:18 Kevin [this message]
2015-02-12  8:27 ` CTRL+Arrow keys don't work with Git Bash for Windows? Sebastian Schuberth

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=loom.20150129T161729-820@post.gmane.org \
    --to=kevin071586@yahoo.com \
    --cc=git@vger.kernel.org \
    /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 NNTP newsgroup(s).