From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: mi tty commands
Date: Wed, 01 Jun 2005 00:14:00 -0000 [thread overview]
Message-ID: <20050601001440.GB15414@white> (raw)
In-Reply-To: <20050529205435.GA11243@white>
On Sun, May 29, 2005 at 04:54:35PM -0400, Bob Rossi wrote:
> On Sun, May 29, 2005 at 09:55:23AM +0300, Eli Zaretskii wrote:
> > > Date: Sat, 28 May 2005 19:08:55 -0400
> > > From: Daniel Jacobowitz <drow@false.org>
> > >
> > > On Sun, May 22, 2005 at 05:00:40PM -0400, Bob Rossi wrote:
> > > > On Thu, Mar 10, 2005 at 09:26:44PM -0500, Bob Rossi wrote:
> > > > > Ping
> > > >
> > > > Ping, and O yeah, I updated the patch the best I could to get the code
> > > > to conform with the GNU coding standards. I hope I'm getting this right.
> > >
> > > Not quite, but I don't mind proofreading :-)
> >
> > Sorry, I somehow managed to miss the original message. My comments
> > are below.
> >
> > > + /* add the filename of the terminal connected to inferior I/O */
> > > + add_setshow_string_noescape_cmd ( "inferior_tty", class_run,
> > > + &inferior_io_terminal, _("\
> > > +Set terminal for future runs of program being debugged."), _("\
> > > +Show terminal for future runs of program being debugged."), _("\
> > > +Usage: set inferior_tty /dev/pts/1"), NULL, NULL, &setlist, &showlist);
> > > + set_cmd_completer (c, filename_completer);
> >
> > You are adding a new user command, but you didn't add its
> > documentation to gdb.texinfo. Please add that; I don't want us to
> > ever have undocumented commands again.
> >
> > And I agree with Daniel: let's get rid of that underscore in the
> > command's name.
>
> Oops, I don't know how I missed that. I added the doco for the MI
> commands and this must have slipped passed me.
>
> I'm having trouble finding a particular spot in the manual for this
> command. Do you have any suggestions?
Eli, is the MI doco good enough? or do you want the doco for set/show?
If you want the set/show doco, please let me know where to put it in the
manual.
Thanks very much,
Bob Rossi
next prev parent reply other threads:[~2005-06-01 0:14 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 20:49 Bob Rossi
2005-02-26 4:33 ` Eli Zaretskii
2005-02-26 6:07 ` Bob Rossi
2005-02-26 8:25 ` Daniel Jacobowitz
2005-02-28 20:28 ` Bob Rossi
2005-03-02 2:52 ` Bob Rossi
2005-03-11 2:26 ` Bob Rossi
2005-05-23 3:13 ` Bob Rossi
2005-05-28 23:49 ` Daniel Jacobowitz
2005-05-29 8:37 ` Eli Zaretskii
2005-05-29 16:22 ` Daniel Jacobowitz
2005-05-29 18:10 ` Eli Zaretskii
2005-05-29 19:05 ` Daniel Jacobowitz
2005-05-30 15:48 ` Bob Rossi
2005-06-01 0:14 ` Bob Rossi [this message]
2005-06-01 4:00 ` Eli Zaretskii
2005-06-01 13:07 ` Bob Rossi
2005-06-01 17:42 ` Bob Rossi
2005-06-01 20:25 ` Eli Zaretskii
2005-06-02 22:17 ` Bob Rossi
2005-06-03 6:48 ` Eli Zaretskii
2005-06-03 17:32 ` Bob Rossi
2005-06-10 2:28 ` Bob Rossi
2005-06-10 6:36 ` Eli Zaretskii
2005-06-10 11:04 ` Bob Rossi
2005-06-13 3:07 ` Daniel Jacobowitz
2005-06-13 6:09 ` Eli Zaretskii
2005-06-17 21:08 ` Bob Rossi
2005-06-17 21:14 ` Daniel Jacobowitz
2005-06-18 8:27 ` Eli Zaretskii
2005-06-18 12:29 ` Bob Rossi
2005-06-26 13:43 ` Bob Rossi
2005-07-03 18:43 ` Daniel Jacobowitz
2005-07-06 14:54 ` Bob Rossi
2005-07-10 21:08 ` Mark Kettenis
2005-07-10 21:32 ` Bob Rossi
2005-07-11 15:52 ` Bob Rossi
2005-07-11 18:41 ` Mark Kettenis
2005-07-11 20:00 ` Bob Rossi
2005-07-11 20:01 ` Daniel Jacobowitz
2005-07-11 20:44 ` Bob Rossi
2005-07-11 20:55 ` Mark Kettenis
2005-07-11 21:26 ` Bob Rossi
2005-07-12 20:56 ` Mark Kettenis
2005-07-14 14:51 ` Bob Rossi
2005-06-01 20:12 ` Eli Zaretskii
2005-06-01 20:43 ` Bob Rossi
2005-06-02 3:48 ` Eli Zaretskii
2005-05-30 15:48 ` Bob Rossi
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=20050601001440.GB15414@white \
--to=bob@brasko.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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