From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Martin Guy <martinwguy@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: single-char options
Date: Sun, 4 Feb 2024 14:47:22 +0100 [thread overview]
Message-ID: <Zb+Vake8k3Lpx3Ut@ugly> (raw)
In-Reply-To: <0e88ac8ad60d2da689d0a308cc59a02d468bc15f.camel@gmail.com>
On Fri, Feb 02, 2024 at 01:45:55PM +0000, Martin Guy wrote:
>I'm sure this must have been thought of before and rejected, but us RSI
>sufferers would like to be able to say "git rebase -c" for "--continue"
>not only for speed and ease, but for all the other RSI sufferers out
>there.
>
you don't need to re-type the commands.
in bash (or any other readline-using shell) just type ctrl-r 'onti' (or
anything else sufficiently unique) and maybe ctrl-r a few times more.
it's very rare that i type repeat commands from scratch. in fact, to the
point that i often spend more time hopping through the history than it
would have taken to re-type the command, heh.
prev parent reply other threads:[~2024-02-05 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:45 single-char options Martin Guy
2024-02-02 14:42 ` Kristoffer Haugsbakk
2024-02-02 14:59 ` Sergey Organov
2024-02-04 13:47 ` Oswald Buddenhagen [this message]
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=Zb+Vake8k3Lpx3Ut@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=git@vger.kernel.org \
--cc=martinwguy@gmail.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 NNTP newsgroup(s).