From: Junio C Hamano <gitster@pobox.com>
To: "Sebastian Schuberth" <sschuberth@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git diff --name-status does not always list changed files
Date: Thu, 28 Feb 2008 14:51:08 -0800 [thread overview]
Message-ID: <7v63w8hezn.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <bdca99240802281419o3fcea2e8u277d8e5e48131b6d@mail.gmail.com> (Sebastian Schuberth's message of "Thu, 28 Feb 2008 23:19:35 +0100")
"Sebastian Schuberth" <sschuberth@gmail.com> writes:
> Thanks, -FX works, though I do not understand why it did not with just
> -F. From what I understood, -F just makes "less" quit immediately
> (instead of waiting for the user to press "q") if the lines to display
> fit completely on screen. In no case it should display nothing if
> there actually is something to display.
My reading and understanding of less manual page, especially the
part that talks about -X suggests that everything is working as
it is meant to.
"git diff --name-status" displays something, less shows it, and
it quits immediately (because you asked it to with -F). As part
of its quitting, it clears the screen because you did not ask
less not to do that by giving it an -X.
I am tempted to call it a bug in less, but I am a very nice
person and I would not actually do so ;-). But it certainly
feels like a misfeature between less and terminfo to me.
prev parent reply other threads:[~2008-02-28 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 14:47 git diff --name-status does not always list changed files Sebastian Schuberth
2008-02-28 19:33 ` Junio C Hamano
2008-02-28 21:23 ` Sebastian Schuberth
2008-02-28 21:42 ` Junio C Hamano
2008-02-28 22:19 ` Sebastian Schuberth
2008-02-28 22:51 ` Junio C Hamano [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
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=7v63w8hezn.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sschuberth@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.
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).