From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)]
Date: Tue, 1 May 2018 13:57:14 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1805011351330.79@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <918c69be-89ce-c66d-92ee-4821e9412793@kdbg.org>
Hi Hannes,
On Mon, 30 Apr 2018, Johannes Sixt wrote:
> Am 30.04.2018 um 05:25 schrieb Junio C Hamano:
> > * js/no-pager-shorthand (2018-04-25) 1 commit
> > - git: add -N as a short option for --no-pager
> >
> > "git --no-pager cmd" did not have short-and-sweet single letter
> > option. Now it does.
> >
> > Will merge to 'next'.
>
> I consider your argument that -N is only an abbreviation for an unspecific
> "no" a valid one. So, I would like to be sure that we are not painting us into
> the wrong corner by squatting -N for --no-pager.
>
> I find -P is not that bad after all.
To me, `-P` would suggest the positive action --pager rather than the
negative --no-pager.
I wonder whether `-!p` would be better/feasible?
Your use case is quite the corner case, I hope you realize that, as it
seems that everybody else is fine with having -FRX as default options for
`less`... And with copy/pasting from the `less` output. So introducing a
sweet short option for --no-pager, for the benefit of maybe even only one
user, seems quite... unusual.
Granted, you cannot simply introduce an alias for `git --no-pager`. But
maybe that is what we should do? Maybe we should start supporting aliases
without specifying commands, opening the door for things like `git -c
ui.color=false`, too.
Then you could add `alias.n=--no-pager` and call `git n show HEAD`, and
the -N and -P short options could still wait for a widely-popular option
to require a short name.
Ciao,
Dscho
next prev parent reply other threads:[~2018-05-01 11:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 3:25 What's cooking in git.git (Apr 2018, #04; Mon, 30) Junio C Hamano
2018-04-30 15:33 ` SZEDER Gábor
2018-05-01 13:46 ` Johannes Schindelin
2018-05-02 3:59 ` Junio C Hamano
2018-05-02 6:53 ` Johannes Schindelin
2018-05-02 10:46 ` Junio C Hamano
2018-05-02 1:36 ` Junio C Hamano
2018-04-30 19:17 ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Johannes Sixt
2018-05-01 11:57 ` Johannes Schindelin [this message]
2018-05-01 14:58 ` Johannes Sixt
2018-05-01 18:10 ` Eric Sunshine
2018-05-02 1:43 ` js/no-pager-shorthand [ Junio C Hamano
2018-05-01 18:46 ` js/no-pager-shorthand [was: What's cooking in git.git (Apr 2018, #04; Mon, 30)] Ævar Arnfjörð Bjarmason
2018-05-02 23:17 ` What's cooking in git.git (Apr 2018, #04; Mon, 30) Brandon Williams
2018-05-04 18:04 ` Elijah Newren
2018-05-07 4:39 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1805011351330.79@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).