From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Never silently discard internal errors
Date: Tue, 26 Sep 2006 03:56:00 -0000 [thread overview]
Message-ID: <20060926035610.GA31294@nevyn.them.org> (raw)
In-Reply-To: <uhcyvl307.fsf@gnu.org>
On Tue, Sep 26, 2006 at 06:29:12AM +0300, Eli Zaretskii wrote:
> > Date: Mon, 25 Sep 2006 16:05:34 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb-patches@sourceware.org
> >
> > I don't think we could start prompting on pipes; I'm sure it would
> > break some things, probably including the emacs mode in question.
>
> Can you elaborate about the breakage?
I don't know what would break for sure, but I imagine that code which
has never before received any "(y or n)" prompts would not know what to
do when it got one, for any operations it conducted on behalf of the
user. This is the sort of thing that causes tests in the testsuite to
time out. The other likely problem is with line buffering; output over
a pipe is on many platforms block buffered rather than line buffered,
and the prompts might fail to show up when they were needed.
This is all speculation! Maybe it would just work, but it doesn't seem
like a great change unless someone who thinks it's a good idea
volunteers to test a bunch of different scenarios, and I'm not that
interested in the issue, I'm afraid.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-09-26 3:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 18:42 Daniel Jacobowitz
2006-09-25 19:10 ` Michael Snyder
2006-09-25 19:37 ` Jim Blandy
2006-09-25 20:03 ` Daniel Jacobowitz
2006-09-25 21:17 ` Jim Blandy
2006-09-26 3:56 ` Daniel Jacobowitz
2006-10-18 22:21 ` Daniel Jacobowitz
2006-09-25 19:43 ` Eli Zaretskii
2006-09-25 20:05 ` Daniel Jacobowitz
2006-09-26 3:29 ` Eli Zaretskii
2006-09-26 3:56 ` Daniel Jacobowitz [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060926035610.GA31294@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.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