From: Ismael Luceno <ismael@iodev.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Pat Thoyts <patthoyts@users.sourceforge.net>
Subject: Re: [PATCH v2] git-gui: Handle Ctrl + BS/Del in the commit msg
Date: Thu, 21 Feb 2019 10:31:00 +0100 [thread overview]
Message-ID: <20190221093059.GA6594@kiki> (raw)
In-Reply-To: <xmqqbm36w7hl.fsf@gitster-ct.c.googlers.com>
On 20/Feb/2019 12:05, Junio C Hamano wrote:
> Ismael Luceno <ismael@iodev.co.uk> writes:
>
> > - Control+BackSpace: Delete word to the left of the cursor.
> > - Control+Delete : Delete word to the right of the cursor.
> >
> > Originally introduced by BRIEF and Turbo Vision between 1985 and 1992,
> > they were adopted by most CUA-Compliant UIs, including those of: OS/2,
> > Windows, Mac OS, Qt, GTK, Open/Libre Office, Gecko, and GNU Emacs.
> >
> > Signed-off-by: Ismael Luceno <ismael@iodev.co.uk>
> > ---
> >
> > Notes:
> > Changes since v1:
> > - Improved commit message.
>
> I do not use git-gui, but as a bystander, the intent of the change
> sounds sane. deleting from the insertion cursor to the end of the
> word where the insertion cursor is looks like the right way to
> delete the word to the right of the cursor. I am not sure if going
> back by one character from where the current insertion cursor is and
> further go back to the wordstart would give the beginning of the
> word to the left of the cursor, though.
Graphical explanation:
Deleting to the left:
v----- pointer
X_WORD_X
^--^------ selection
Deleting to the right:
v--------- pointer
X_WORD_X
^--^------ selection
Current implementation doesn't behave correctly when there's multiple
spaces:
Deleting to the left:
v--- pointer
X_WORD____X
^---- selection
Deleting to the right:
v--------- pointer
X____WORD_X
^--------- selection
> A larger issue is that we haven't heard from Pat, who has been
> helping git-gui.sh maintenance, for quite a while, so we'd need to
> find a volunteer to act as a replacement maintainer. If you are
> willing to, that would be great ;-)
Sure.
next prev parent reply other threads:[~2019-02-21 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 3:10 [PATCH v2] git-gui: Handle Ctrl + BS/Del in the commit msg Ismael Luceno
2019-02-20 20:05 ` Junio C Hamano
2019-02-21 9:31 ` Ismael Luceno [this message]
2019-02-21 20:47 ` Junio C Hamano
2019-03-04 14:09 ` Ismael Luceno
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=20190221093059.GA6594@kiki \
--to=ismael@iodev.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=patthoyts@users.sourceforge.net \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.