From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
solsTiCe d'Hiver <solstice.dhiver@gmail.com>
Subject: Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell
Date: Thu, 29 Jul 2010 22:29:36 +0100 [thread overview]
Message-ID: <4C51F2C0.8090101@pileofstuff.org> (raw)
In-Reply-To: <7v4ofiuuf7.fsf@alter.siamese.dyndns.org>
On 29/07/10 17:25, Junio C Hamano wrote:
>
> I do agree that there need to be a way to find that information for the
> end users, especially for those who just use binary-packaged git given by
> their distros, but this codepath is _not_ the place to do it.
>
> How about replacing these with something simple like:
>
> echo >&2 "You are not running full 'bash'; exiting." ; exit 127
I take your point that this is not the place to advertise the mailing
list, although I prefer to include instructions in error messages.
Would you be amenable in principle to creating something like `man
git-bug`? A quick search doesn't turn up any documents specifically
about bug fixing/reporting, and a man page was the first place I thought
to look. I'll happily withdraw this patch until I can have a crack at
such a page.
>> + BASH_VERSION: {$BASH_VERSION}
>> + BASHOPTS: {$BASHOPTS}
>> + SHELLOPTS: {$SHELLOPTS}
>> + POSIXLY_CORRECT: {$POSIXLY_CORRECT}
>> +EOF
>> + echo -n " command line: {"
>> + tr '\0' ' ' < /proc/$$/cmdline
>
> This looks like a Linux-ism to me.
Caught red-flippered :) I'll use `ps` next time.
- Andrew
next prev parent reply other threads:[~2010-07-29 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 22:32 [PATCH] bash-completion: Print a useful error when called in a non-bash shell Andrew Sayers
2010-07-29 16:25 ` Junio C Hamano
2010-07-29 19:05 ` solsTiCe d'Hiver
2010-07-29 21:29 ` Andrew Sayers [this message]
2010-07-29 22:16 ` Ævar Arnfjörð Bjarmason
2010-07-29 23:38 ` Junio C Hamano
2010-07-30 6:02 ` Stephen Boyd
2010-08-06 21:31 ` Johannes Sixt
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=4C51F2C0.8090101@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=solstice.dhiver@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.
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).