Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15761

Re: Fwd: read -t 0 fails to detect input.

Path csiph.com!fu-berlin.de!usenet.stanford.edu!not-for-mail
From Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups gnu.bash.bug
Subject Re: Fwd: read -t 0 fails to detect input.
Date Fri, 20 Dec 2019 09:55:40 -0500
Lines 18
Approved bug-bash@gnu.org
Message-ID <mailman.1187.1576853771.1979.bug-bash@gnu.org> (permalink)
References <CAFra36gNku2DTCyivz+caMGnTf7GvGJUTiWicUnBZatcckXGcQ@mail.gmail.com> <7e6fccb4-e5b5-eb2b-8b12-eeee9d638ae1@case.edu> <CAFra36iJqGfocqtVYqcdfkePJZ5xrWg8=pfKZXymD34Gaz02rA@mail.gmail.com> <CAFra36iUQqc-yUmZyu-3ty15jWiN=5o_XQ8pxLsZieEZP8=Lsw@mail.gmail.com> <20191220085747.1401a8011f54209747d32617@schrader-schulte.de> <CAFra36iHt+ah0xV7aUXrJh+CEU+fFEW1Xi=yYsOCu7x9+AVqMA@mail.gmail.com> <20191220145540.GT851@eeg.ccf.org>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Trace usenet.stanford.edu 1576853771 8934 209.51.188.17 (20 Dec 2019 14:56:11 GMT)
X-Complaints-To action@cs.stanford.edu
To bug-bash@gnu.org
Envelope-to bug-bash@gnu.org
Mail-Followup-To bug-bash@gnu.org
Content-Disposition inline
In-Reply-To <CAFra36iHt+ah0xV7aUXrJh+CEU+fFEW1Xi=yYsOCu7x9+AVqMA@mail.gmail.com>
User-Agent Mutt/1.10.1 (2018-07-13)
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy]
X-Received-From 139.137.100.1
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <20191220145540.GT851@eeg.ccf.org>
X-Mailman-Original-References <CAFra36gNku2DTCyivz+caMGnTf7GvGJUTiWicUnBZatcckXGcQ@mail.gmail.com> <7e6fccb4-e5b5-eb2b-8b12-eeee9d638ae1@case.edu> <CAFra36iJqGfocqtVYqcdfkePJZ5xrWg8=pfKZXymD34Gaz02rA@mail.gmail.com> <CAFra36iUQqc-yUmZyu-3ty15jWiN=5o_XQ8pxLsZieEZP8=Lsw@mail.gmail.com> <20191220085747.1401a8011f54209747d32617@schrader-schulte.de> <CAFra36iHt+ah0xV7aUXrJh+CEU+fFEW1Xi=yYsOCu7x9+AVqMA@mail.gmail.com>
Xref csiph.com gnu.bash.bug:15761

Show key headers only | View raw


On Fri, Dec 20, 2019 at 10:40:26AM -0400, Bize Ma wrote:
> I am not the one making those comments. I don't have enough C expertise
> to neither confirm or deny them. But that also makes me unable to answer to
> the
> author of the comments in the proper way. I intended to receive something to
> correct his (incorect?) opinion.

It's not your job to correct someone else's erroneous statements.
Don't waste your time acting as a middleman, or trying to clean up
all of the misinformation on the Internet.  There's too much of it
for anyone to handle.

If you have a specific goal you're trying to accomplish, tell us what
that goal is, and maybe we can help you get it done.

If there's something you don't understand, tell us what that is, and
maybe we can help you understand it.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Fwd: read -t 0 fails to detect input. Greg Wooledge <wooledg@eeg.ccf.org> - 2019-12-20 09:55 -0500

csiph-web