From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: MI -break-info command issues
Date: Fri, 27 Jan 2006 15:00:00 -0000 [thread overview]
Message-ID: <20060127145627.GA30826@brasko.net> (raw)
In-Reply-To: <ufyn9euj6.fsf@gnu.org>
On Fri, Jan 27, 2006 at 02:15:41PM +0200, Eli Zaretskii wrote:
> > Can you name frontend that uses MI and that is not GUI, just as example.
>
> Why should I bother? MI is a general-purpose interface, it's not
> limited to GUI. That's its design goal. Even if there's no UI at
> this time that uses MI, it doesn't necessarily mean we should forever
> ban such UIs from coming into existence, just because there are a few
> fields a GUI normally won't want.
I agree that the data is useless. However, Eli's concern is that it
might not be useless to a particular program that is already using it.
If we remove it, I'm sure the developer (of the program that uses the
data) wouldn't be happy. Does it really hurt to leave it there?
I will just ignore it.
However, I do have an opinion that new commands should not contain
formatting data like this. It's pushing mechanism over policy.
http://www.faqs.org/docs/artu/ch01s06.html#id2877777
Bob Rossi
next prev parent reply other threads:[~2006-01-27 14:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 14:22 Vladimir Prus
2006-01-24 14:48 ` Bob Rossi
2006-01-24 15:02 ` Vladimir Prus
2006-01-24 21:24 ` Eli Zaretskii
2006-01-24 23:35 ` Bob Rossi
2006-01-25 16:05 ` Vladimir Prus
2006-01-25 19:42 ` Eli Zaretskii
2006-01-26 12:09 ` Vladimir Prus
2006-01-26 20:48 ` Eli Zaretskii
2006-01-27 12:16 ` Vladimir Prus
2006-01-27 14:55 ` Eli Zaretskii
2006-01-27 15:00 ` Bob Rossi [this message]
2006-01-27 15:12 ` Vladimir Prus
2006-01-27 15:48 ` Daniel Jacobowitz
2006-01-27 15:51 ` Vladimir Prus
2006-01-27 16:11 ` Daniel Jacobowitz
2006-01-27 16:01 ` Daniel Jacobowitz
2006-01-27 16:44 ` Vladimir Prus
2006-01-27 17:00 ` Bob Rossi
2006-02-10 12:03 ` Documenting MI stability (Was: MI -break-info command issues) Vladimir Prus
2006-01-27 17:41 ` MI -break-info command issues Eli Zaretskii
2006-01-27 17:16 ` Eli Zaretskii
2006-01-27 17:53 ` Bob Rossi
2006-01-28 14:48 ` Eli Zaretskii
2006-01-27 17:12 ` Eli Zaretskii
2006-03-17 17:07 ` -data-read-memory docs (Was: MI -break-info command issues) Vladimir Prus
2006-03-18 11:26 ` Eli Zaretskii
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=20060127145627.GA30826@brasko.net \
--to=bob@brasko.net \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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