Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -stack-select-frame
Date: Fri, 17 Jun 2005 13:33:00 -0000	[thread overview]
Message-ID: <20050617133311.GB23901@nevyn.them.org> (raw)
In-Reply-To: <umzpp1bgv.fsf@gnu.org>

On Fri, Jun 17, 2005 at 01:14:56PM +0200, Eli Zaretskii wrote:
> > From: Nick Roberts <nickrob@snap.net.nz>
> > Date: Fri, 17 Jun 2005 19:39:00 +1200
> > Cc: gdb-patches@sources.redhat.com
> > 
> >  > > -stack-info-frame hasn't been implemented yet (I've think we've been here
> >  > > before) but it would probably be quite easy to implement and I guess it
> >  > > could work like I've made -stack-select-frame without an argument work.
> >  > 
> >  > *snicker* that's what I get for reading the manual.  I assumed it was
> >  > implemented.
> >  > 
> >  > Maybe it is time to mark the unimplemented commands in the manual?
> > 
> > It _is_ documented as unimplemented in my copy.
> 
> Well, not really ``documented as''.  The manual says that commands
> whose "Example" section says "N.A." are not implemented, but a reader
> who reads a description of a certain command will not necessarily
> deduce that.

It took me a few minutes poking through the manual to find this, even
after you told me it was there...

> I think we should simply @ignore-out such commands.

I'm OK with that, especially if you prefer it.  I'd like to either do
that, or expand the N.A. to be explicit ("N.A.@: - not implemented
yet").

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-17 13:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16  3:36 Nick Roberts
2005-06-16  4:42 ` Daniel Jacobowitz
2005-06-16  6:41   ` Nick Roberts
2005-06-16 13:21     ` Daniel Jacobowitz
2005-06-16 22:58       ` Nick Roberts
2005-06-16 23:20         ` Bob Rossi
2005-06-16 23:47         ` Daniel Jacobowitz
2005-06-17  3:07           ` Nick Roberts
2005-06-17  3:21             ` Daniel Jacobowitz
2005-06-17  7:37               ` Nick Roberts
2005-06-17 10:15                 ` Eli Zaretskii
2005-06-17 13:33                   ` Daniel Jacobowitz [this message]
2005-06-18  8:56                     ` Eli Zaretskii
2005-06-17  9:55               ` Eli Zaretskii
2005-06-17  9:46             ` Eli Zaretskii
2005-06-16 18:23 ` Eli Zaretskii
2005-06-16 20:15 ` Jason Molenda
2005-06-16 23:04   ` Nick Roberts
2005-06-16 23:30     ` Jason Molenda
2005-06-17  7:22       ` Nick Roberts
2005-06-17 13:30         ` Daniel Jacobowitz
2005-06-17 19:48         ` Jason Molenda
2005-06-17 22:35         ` Stan Shebs
2005-06-17 22:59           ` Daniel Jacobowitz
2005-06-17 23:31           ` Nick Roberts
     [not found] <1119003319.5434.ezmlm@sources.redhat.com>
2005-06-17 17:45 ` Jim Ingham

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=20050617133311.GB23901@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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