Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "André Pönitz" <andre.poenitz@nokia.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Implement -exec-jump
Date: Wed, 08 Apr 2009 11:46:00 -0000	[thread overview]
Message-ID: <83y6ub4bjo.fsf@gnu.org> (raw)
In-Reply-To: <200904081305.41964.andre.poenitz@nokia.com>

> From: =?iso-8859-1?q?Andr=E9_P=F6nitz?= <andre.poenitz@nokia.com>
> Date: Wed, 8 Apr 2009 12:05:41 +0100
> 
> I personally pretty much prefer progress on the MI implementation
> side, if that means a few days delay on the documentation,
> (or even a small risk of having no documentation at all(!)),
> so I am _personally_ fine with it.

If that turns out to be the opinion of the majority of GDB users, I'll
probably resign as the docs maintainer, because putting in all those
efforts when no one needs them is waste of my scarce free time.

> That's a interesting proposal. There is so much stuff, basic stuff 
> even, undocumented, so Joe Frontend has to read the sources 
> anyway.

As long as I am responsible for the documentation here, I urge you to
report any such cases, and I will try to improve the docs as well as I
can.

> As an example: The quoting rules for the CLI are completely 
> opaque, but, giving the de-facto non-existence of a binary
> interface to gdb, crucial for any frontend.  A frontend can
> not just go "type a command" - "hey, gdb does not like it, so 
> try to put in a quote or two"...

Typing "i quot TAB" in the Info reader of the GDB manual brings up the
"quotes in commands" index entry, which leads to a place that has some
documentation of quoting.  I'm not saying that this is what you need,
but please tell what details are missing from what it says there.


  reply	other threads:[~2009-04-08 11:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  5:50 Vladimir Prus
2009-04-08  6:55 ` Eli Zaretskii
2009-04-08  7:08   ` Vladimir Prus
2009-04-08  7:22     ` Eli Zaretskii
2009-04-08  7:36       ` Vladimir Prus
2009-04-08  9:00         ` Eli Zaretskii
2009-04-08 16:26           ` Tom Tromey
2009-04-22 12:57           ` Vladimir Prus
2009-04-22 17:26             ` Eli Zaretskii
2009-04-08  9:16       ` André Pönitz
2009-04-08  9:29         ` Eli Zaretskii
2009-04-08 11:05           ` André Pönitz
2009-04-08 11:46             ` Eli Zaretskii [this message]
2009-04-08 21:51           ` Thiago Jung Bauermann
2009-04-08 21:57             ` Joel Brobecker
2009-04-10 16:50               ` Eli Zaretskii
2009-04-13 17:24                 ` Tom Tromey
2009-04-08 16:28         ` Tom Tromey
2009-04-08 22:03   ` Thiago Jung Bauermann
2009-04-22 12:09 ` Vladimir Prus
2009-04-22 17:16   ` Eli Zaretskii

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=83y6ub4bjo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andre.poenitz@nokia.com \
    --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