From: Junio C Hamano <gitster@pobox.com>
To: Anders Melchiorsen <mail@cup.kalibalik.dk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH RESEND] Do not override LESS
Date: Sat, 23 Aug 2008 02:08:58 -0700 [thread overview]
Message-ID: <7vtzdc14k5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87k5e8i18c.fsf@cup.kalibalik.dk> (Anders Melchiorsen's message of "Sat, 23 Aug 2008 10:28:51 +0200")
Anders Melchiorsen <mail@cup.kalibalik.dk> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> 3. Christ has been happily using git with his PAGER set to "less". He
>> suddenly notices that output from git linewraps and the pager does not
>> exit when showing a short output, and gets very unhappy.
>
> Well, I noted that point already, so I had hoped for a reply
> explaining why it is a big problem.
It is a huge problem. It breaks people's existing perfectly well working
setup.
And I do not think it is impossible to solve the issue without doing so.
> While I am wary of advocating a patch that makes Christ unhappy, the
> "3." issue is easily fixed by him setting GIT_PAGER="less -FRSX".
That's not a solution. Alice and Bob can also change their environment to
their taste as well. Why punish existing users?
If the problem you are trying to solve is that there is no existing
combination of the environment variables for them to do so, you can solve
it by introducing a new configuration or environment to support such usage
and documenting it, can't you?
next prev parent reply other threads:[~2008-08-23 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 12:25 [PATCH RESEND] Do not override LESS Anders Melchiorsen
2008-08-23 5:35 ` Junio C Hamano
2008-08-23 8:28 ` Anders Melchiorsen
2008-08-23 9:08 ` Junio C Hamano [this message]
2008-08-23 10:21 ` Anders Melchiorsen
2008-08-24 5:28 ` Jonathan Nieder
2008-08-24 5:38 ` [PATCH] Documentation: clarify pager.<cmd> configuration Jonathan Nieder
2008-08-24 18:59 ` [PATCH RESEND] Do not override LESS 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vtzdc14k5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mail@cup.kalibalik.dk \
/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).