From: Nick Roberts <nickrob@snap.net.nz>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Vladimir Prus <ghost@cs.msu.su>,
gdb-patches@sources.redhat.com
Subject: Re: cleanup mi error message handling
Date: Tue, 01 Apr 2008 13:17:00 -0000 [thread overview]
Message-ID: <18417.39191.771661.246135@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200804010118.22536.pedro@codesourcery.com>
> > Other errors like:
> >
> > (gdb)
> > -interpreter-exec
> > ^error,msg="mi_cmd_interpreter_exec: Usage: -interpreter-exec interp
> > command" (gdb)
> >
> > would be due to a frontend error, so I think it would be probably be best
> > to display them elsewhare, e.g., status bar.
> >
>
> I think the screen should flash and beep three times, and an email
> should be automatically sent the the frontend author :-) Seriously,
> the status bar doesn't feel right for this. This is not status.
Please don't take the status bar example too literally, it was just the first
place I thought of, and is not the focus of my message.
To get a meaningful report probably requires full logging of all the
transactions anyway, which is what I do for Emacs.
In any case I've already surrendered on this issue.
Please redirect any frontend errors using Gdb in Emacs reported on this list to
emacs-devel ;-)
Thanks.
--
Nick http://www.inet.net.nz/~nickrob
WARNING: multiple messages have this Message-ID
From: Nick Roberts <nickrob@snap.net.nz>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Vladimir Prus <ghost@cs.msu.su>,
gdb-patches@sources.redhat.com
Subject: Re: cleanup mi error message handling
Date: Tue, 01 Apr 2008 03:28:00 -0000 [thread overview]
Message-ID: <18417.39191.771661.246135@kahikatea.snap.net.nz> (raw)
Message-ID: <20080401032800.l4nxWHrxc3gd96kryZpMt06xdgf4QAUKAzOgunywifI@z> (raw)
In-Reply-To: <200804010118.22536.pedro@codesourcery.com>
> > Other errors like:
> >
> > (gdb)
> > -interpreter-exec
> > ^error,msg="mi_cmd_interpreter_exec: Usage: -interpreter-exec interp
> > command" (gdb)
> >
> > would be due to a frontend error, so I think it would be probably be best
> > to display them elsewhare, e.g., status bar.
> >
>
> I think the screen should flash and beep three times, and an email
> should be automatically sent the the frontend author :-) Seriously,
> the status bar doesn't feel right for this. This is not status.
Please don't take the status bar example too literally, it was just the first
place I thought of, and is not the focus of my message.
To get a meaningful report probably requires full logging of all the
transactions anyway, which is what I do for Emacs.
In any case I've already surrendered on this issue.
Please redirect any frontend errors using Gdb in Emacs reported on this list to
emacs-devel ;-)
Thanks.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-04-01 2:09 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
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 [this message]
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=18417.39191.771661.246135@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ghost@cs.msu.su \
--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