git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Olaf Meeuwissen <olaf.meeuwissen@avasys.jp>,
	git@vger.kernel.org
Subject: Re: [PATCH] pager: set LV=-c alongside LESS=FRSX
Date: Tue, 07 Jan 2014 19:17:09 +0100	[thread overview]
Message-ID: <87iotvbqsa.fsf@igel.home> (raw)
In-Reply-To: <xmqqha9fg225.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Tue, 07 Jan 2014 09:00:02 -0800")

Junio C Hamano <gitster@pobox.com> writes:

>  - Scripted Porcelains get LESS=-FRSX while C Porcelains get
>    LESS=FRSX as the default (the leading dash being the
>    difference), which looks somewhat inconsistent.  Not a new
>    problem, though.

Even the less manpage is inconsistent about whether $LESS should start
with a dash (there are examples with and without it).
Implementation-wise, less uses the same function to process an option
argument (including the leading dash) and the value of $LESS, so the
form with the leading dash is probably preferred.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2014-01-07 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874n6zbqlh.fsf@helix.nebula.avasys.jp>
     [not found] ` <20140106193339.GH3881@google.com>
     [not found]   ` <874n5ghenr.fsf@helix.nebula.avasys.jp>
2014-01-07  2:14     ` [PATCH] pager: set LV=-c alongside LESS=FRSX Jonathan Nieder
2014-01-07  4:09       ` Olaf Meeuwissen
2014-01-07 17:00       ` Junio C Hamano
2014-01-07 18:17         ` Andreas Schwab [this message]
2014-01-30  7:15       ` Anders Kaseorg
2014-01-30 16:42         ` [PATCH jn/pager-lv-default-env] pager test: make fake pager consume all its input Jonathan Nieder
2014-01-31 17:07           ` 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=87iotvbqsa.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=olaf.meeuwissen@avasys.jp \
    /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).