From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: cleanup mi error message handling
Date: Mon, 24 Mar 2008 23:37:00 -0000 [thread overview]
Message-ID: <18408.15132.721049.31408@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080324223840.GA20307@caradoc.them.org>
> > because the first goes to the console for the user to see, the second to
> > the frontend to be handled as appropriate.
>
> Could you explain why the duplication here is good? It seems to me
> that if the front end wants to display this error to the user in the
> console, it can do so anyway, but it shouldn't have to. Maybe this
> requires a version bump, I don't know.
Emacs isn't currently using this output, so I'm not speaking from experience,
but how does the front end determine which messages are for the user?
Currently most messages that are due to frontend errors go through error ()
so I guess I'm suggesting the opposite change!
> In Eclipse, this duplication leads to a bunch of error messages that
> pop up in the console pane which don't come from anything the user
> did. It's very confusing.
Just as you say if the "frontend wants to display this error to the user in
the console, it can do so anyway" isn't it equally true that if it doesn't want
to display this error, it can choose not to so?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-03-24 23:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:30 Pedro Alves
2008-03-24 19:08 ` Pedro Alves
2008-03-24 22:04 ` Nick Roberts
2008-03-24 22:39 ` Daniel Jacobowitz
2008-03-24 23:37 ` Nick Roberts [this message]
2008-03-25 1:00 ` Daniel Jacobowitz
2008-03-25 1:29 ` Nick Roberts
2008-03-25 2:12 ` Daniel Jacobowitz
2008-03-29 14:22 ` Vladimir Prus
2008-03-30 5:13 ` Nick Roberts
2008-03-30 6:06 ` Vladimir Prus
2008-03-31 0:46 ` Nick Roberts
2008-03-31 1:59 ` Daniel Jacobowitz
2008-03-31 2:23 ` Nick Roberts
2008-03-31 5:07 ` Vladimir Prus
2008-03-31 6:36 ` Nick Roberts
2008-03-31 7:10 ` Vladimir Prus
2008-03-31 15:17 ` Pedro Alves
2008-03-31 11:24 ` Pedro Alves
2008-04-01 2:00 ` Pedro Alves
2008-04-01 0:18 ` Pedro Alves
2008-04-01 13:17 ` Nick Roberts
2008-04-01 3:28 ` Nick Roberts
2008-03-25 3:52 ` Pedro Alves
2008-04-04 13:33 ` Vladimir Prus
2008-04-04 23:08 ` Pedro Alves
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=18408.15132.721049.31408@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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