From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Never silently discard internal errors
Date: Tue, 26 Sep 2006 03:29:00 -0000 [thread overview]
Message-ID: <uhcyvl307.fsf@gnu.org> (raw)
In-Reply-To: <20060925200534.GB18759@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 25 Sep 2006 16:05:34 -0400)
> 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?
next prev parent reply other threads:[~2006-09-26 3:29 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 [this message]
2006-09-26 3:56 ` Daniel Jacobowitz
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=uhcyvl307.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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