Jeff King p...@peff.net writes:
On Tue, May 06, 2014 at 08:49:22PM +0200, Matthieu Moy wrote:
...
The idea of having a separate default value for pager.blame (or set
$LESS differently for blame) crossed my mind, but I actually don't like
it, as it would make it harder for a user to fine-tune
Junio C Hamano gits...@pobox.com writes:
While I fully agree with the above conclusion, I just noticed that I
will be irritated enough to eventually set pager.blame myself, after
running a short git blame -L1311,+7 git-p4.py, which is one of the
standard first steps for me to start reading
Matthieu Moy matthieu@grenoble-inp.fr writes:
Perhaps it deserves a mention in the doc, e.g. squashing this on top of
my patch:
Thanks, will do.
diff --git a/Documentation/config.txt b/Documentation/config.txt
index b7f92ac..ebd1676 100644
--- a/Documentation/config.txt
+++
Matthieu Moy matthieu@grenoble-inp.fr writes:
By default, Git used to set $LESS to -FRSX if $LESS was not set by the
user. The FRX flags actually make sense for Git (F and X because Git
sometimes pipes short output to less, and R because Git pipes colored
output). The S flag (chop
Junio C Hamano gits...@pobox.com writes:
I still find the output from git blame disturbing, though. The
first thing I do in git blame output is to scroll to the right in
order to identify the the area I am interested in, and this first
step is not negatively affected, because the right
David Kastrup d...@gnu.org writes:
Junio C Hamano gits...@pobox.com writes:
I still find the output from git blame disturbing, though. The
first thing I do in git blame output is to scroll to the right in
order to identify the the area I am interested in, and this first
step is not
On Tue, May 06, 2014 at 08:49:22PM +0200, Matthieu Moy wrote:
Exactly. I personally never use git blame outside git gui blame for
this reason.
I'd recommend tig blame for this, too, which behaves like less -S
with respect to long lines (and also makes it easy to jump to the full
diff, or
Hi,
Matthieu Moy wrote:
By default, Git used to set $LESS to -FRSX if $LESS was not set by the
user. The FRX flags actually make sense for Git (F and X because Git
sometimes pipes short output to less, and R because Git pipes colored
output). The S flag (chop long lines), on the other hand,
- Original Message -
Hi,
Matthieu Moy wrote:
By default, Git used to set $LESS to -FRSX if $LESS was not set by the
user. The FRX flags actually make sense for Git (F and X because Git
sometimes pipes short output to less, and R because Git pipes colored
output). The S flag
By default, Git used to set $LESS to -FRSX if $LESS was not set by the
user. The FRX flags actually make sense for Git (F and X because Git
sometimes pipes short output to less, and R because Git pipes colored
output). The S flag (chop long lines), on the other hand, is not related
to Git and is a
Matthieu Moy matthieu@imag.fr writes:
By default, Git used to set $LESS to -FRSX if $LESS was not set by the
user. The FRX flags actually make sense for Git (F and X because Git
sometimes pipes short output to less, and R because Git pipes colored
output). The S flag (chop long lines), on
Junio C Hamano gits...@pobox.com writes:
Matthieu Moy matthieu@imag.fr writes:
By default, Git used to set $LESS to -FRSX if $LESS was not set by the
user. The FRX flags actually make sense for Git (F and X because Git
sometimes pipes short output to less, and R because Git pipes colored
Matthieu Moy matthieu@grenoble-inp.fr writes:
Junio C Hamano gits...@pobox.com writes:
Matthieu Moy matthieu@imag.fr writes:
By default, Git used to set $LESS to -FRSX if $LESS was not set by the
user. The FRX flags actually make sense for Git (F and X because Git
sometimes pipes
13 matches
Mail list logo
