From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: bob@brasko.net
Cc: gdb-patches@sources.redhat.com
Subject: Re: mi tty commands
Date: Mon, 11 Jul 2005 18:41:00 -0000 [thread overview]
Message-ID: <200507111840.j6BIeojH024633@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050711155155.GA32323@white> (message from Bob Rossi on Mon, 11 Jul 2005 11:51:55 -0400)
Date: Mon, 11 Jul 2005 11:51:55 -0400
From: Bob Rossi <bob@brasko.net>
> Bob, please make sure there are no regressions from your patch before
> you check things in. I now get:
>
> FAIL: gdb.base/default.exp: tty
> FAIL: gdb.base/help.exp: help tty
>
> because the output of the tty command changed. In the past we had:
>
> (gdb) tty
> Argument required (terminal name for running target process).
>
> whereas now we have
>
> (gdb) tty
> Argument required (filename to set it to.).
>
> I don't really consider this an improvement...
Does anyone know why the "tty" command gives the "default" message when
I have,
/* add the filename of the terminal connected to inferior I/O */
add_setshow_filename_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);
add_com_alias ("tty", "set inferior-tty", class_alias, 0);
I would expect the alias to take on the usage note from the command it
points to. Either that, or allow me to explicitly give it a usage note.
Any suggestions?
But it does take the usage nore from the command it points to:
(gdb) set inferior-tty
Argument required (filename to set it to.).
Mark
next prev parent reply other threads:[~2005-07-11 18:41 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
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 [this message]
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=200507111840.j6BIeojH024633@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=bob@brasko.net \
--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