From: "Mikael Magnusson" <mikachu@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Francis Moreau" <francis.moro@gmail.com>, git@vger.kernel.org
Subject: Re: git-bisect: weird usage of read(1)
Date: Mon, 11 Aug 2008 16:16:50 +0200 [thread overview]
Message-ID: <237967ef0808110716l2a0a2a4je22c2a1b8c239f57@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0808111615260.24820@pacific.mpi-cbg.de.mpi-cbg.de>
2008/8/11 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> Hi,
>
> On Mon, 11 Aug 2008, Francis Moreau wrote:
>
>> I found this in git bisect:
>>
>> printf >&2 'Are you sure [Y/n]? '
>> case "$(read yesno)" in [Nn]*) exit 1 ;; esac
>>
>> which looks very weird since read(1) returns a status and not the
>> string reads from std input.
>>
>> Am I missing something ?
>
> Yes. "$()" does not return the status, but the output.
But there is no output, since read doesn't print anything...
case "$(read yesno; echo $yesno)" in [Nn]*) could work, but looks
a bit strange. read yesno; case $yesno in [Nn]*) would be the usual
way to do things i think?
--
Mikael Magnusson
next prev parent reply other threads:[~2008-08-11 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 13:57 git-bisect: weird usage of read(1) Francis Moreau
2008-08-11 14:15 ` Johannes Schindelin
2008-08-11 14:16 ` Mikael Magnusson [this message]
2008-08-11 14:18 ` Francis Moreau
2008-08-11 15:59 ` Reece Dunn
2008-08-11 16:23 ` Francis Moreau
2008-08-11 16:26 ` Reece Dunn
2008-08-11 16:29 ` Francis Moreau
2008-08-11 16:49 ` Petr Baudis
2008-08-11 17:01 ` René Scharfe
2008-08-11 17:05 ` Petr Baudis
2008-08-11 18:59 ` Junio C Hamano
2008-08-11 19:47 ` Francis Moreau
2008-08-11 16:18 ` René Scharfe
2008-08-11 17:38 ` Francis Moreau
-- strict thread matches above, loose matches on Subject: below --
2008-08-11 14:00 Francis Moreau
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=237967ef0808110716l2a0a2a4je22c2a1b8c239f57@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=francis.moro@gmail.com \
--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 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).