From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: fatal output from git-show really wants a terminal
Date: Thu, 11 Dec 2008 10:51:15 -0600 [thread overview]
Message-ID: <200812111051.20322.bss03@volumehost.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0812111015140.18321@eeepc-johanness>
[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]
On Thursday 2008 December 11 03:15:47 you wrote:
>On Wed, 10 Dec 2008, Boyd Stephen Smith Jr. wrote:
>> On Wednesday 2008 December 10 13:46:50 you wrote:
>> >On Mittwoch, 10. Dezember 2008, Tim Olsen wrote:
>> >> It appears that when outputting a fatal error, git-show will choose
>> >> stdout over stderr if stdout is a terminal and stderr is not.
>> >
>> >This is by design.
>>
>> Then it is poor design. :P j/k
>
>Read up on the reasoning before trolling, will ya? It's all in the Git
>history.
Seeing how I'm new, and this message indicated I had screwed up, I starting
going through the 'git log' looking for a commit message that either
documented this behavior, or indicated the commit had documented this
behavior.
Initially, I was looking for 'stdout' or 'stderr', and found many unrelated
commits. I then figured it was part of the PAGER support, and began
searching for that. I did find an indication of why stdout and stderr are
both redirected to the PAGER's stdin -- but that makes sense to me; I wasn't
questioning it. At least not too much -- but when the user indicates stderr
and stdout should go to different locations, shouldn't they?
I was mainly questioning using a pager AT ALL when the git command is used in
a non-interactive environment, and how git detects an interactive invocation.
I feel this should be done the same way a (POSIX standard) shell detects
interactivity, and that in a non-interactive environment git should not
default to using PAGER.
Now, I certainly could have missed the commit message / commit with
rationale / documentation. 'git log' output is a long document, and I maybe
using the wrong keywords for my search. It also is not all the documentation
that is out there. I'm not afraid to RTFM; but I'm not having much luck
finding the right parts to R.
Finally, I didn't mean to offend. I was hoping the smiley (":P") and "j/k"
would indicate that a was only half serious and know that I don't have the
benefit of following the project closely for very long. I'm appreciative of
the hard work that goes into git and don't mean to belittle that effort.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-11 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 16:01 fatal output from git-show really wants a terminal Tim Olsen
2008-12-10 16:10 ` Boyd Stephen Smith Jr.
2008-12-10 19:46 ` Johannes Sixt
2008-12-10 20:10 ` Tim Olsen
2008-12-10 22:24 ` Boyd Stephen Smith Jr.
[not found] ` <alpine.DEB.1.00.0812111015140.18321@eeepc-johanness>
2008-12-11 16:51 ` Boyd Stephen Smith Jr. [this message]
2008-12-11 21:55 ` Jeff King
2008-12-11 22:45 ` Boyd Stephen Smith Jr.
2008-12-11 22:59 ` Jeff King
2008-12-11 23:03 ` Junio C Hamano
2008-12-15 8:15 ` Junio C Hamano
2008-12-15 8:23 ` Junio C Hamano
2008-12-15 8:25 ` Jeff King
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=200812111051.20322.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.