Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI Doco
Date: Fri, 02 Jun 2006 10:44:00 -0000	[thread overview]
Message-ID: <u3benet0j.fsf@gnu.org> (raw)
In-Reply-To: <17536.4472.263731.425097@kahikatea.snap.net.nz> (message from 	Nick Roberts on Fri, 2 Jun 2006 22:22:48 +1200)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Fri, 2 Jun 2006 22:22:48 +1200
> Cc: gdb-patches@sources.redhat.com
> 
> I've just noticed that the commands left in "Program Control" are the
> asynchronous ones.  Perhaps something should be said about that.  Actually as
> I read through I see a lot of thing that I want to change, but I'll send these
> changes together.

Thanks.  The MI docs indeed needs a lot of work, so any improvements
are highly appreciated.

>  > > Having repeatedly spent too much time looking for
>  > > -file-list-exec-source-files
>  > 
>  > How do you search?  Index search (the `i' command in Info) should land
>  > you on the right spot no matter in what node that is.
> 
> I've had trouble remembering the exact name too!

Please describe how you searched for it, then.  Good indexing should
make it very easy, even if the exact name is not known, but to suggest
additional index entries, I must know what words or phrases did you
remember/think about.


  reply	other threads:[~2006-06-02 10:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-02  0:23 Nick Roberts
2006-06-02  9:05 ` Eli Zaretskii
2006-06-02 10:23   ` Nick Roberts
2006-06-02 10:44     ` Eli Zaretskii [this message]
2006-06-03 23:57       ` Nick Roberts
2006-06-04 19:32         ` Eli Zaretskii
2006-06-09 19:07         ` Eli Zaretskii
2006-06-09 19:12           ` Daniel Jacobowitz
2006-06-09 19:52             ` Eli Zaretskii
2006-06-09 19:57               ` Daniel Jacobowitz
2006-06-10  7:32                 ` Eli Zaretskii
2006-07-01 12:35                   ` [commit] Fix MI prompt in manual (was: MI Doco) Eli Zaretskii
2006-06-09 19:58               ` [PATCH] MI Doco Bob Rossi
2006-06-09 23:27           ` Nick Roberts
2006-06-10  7:51             ` Eli Zaretskii
2006-06-10 21:40               ` Nick Roberts
2006-06-11  3:31                 ` Eli Zaretskii
2006-06-11 10:47                   ` Nick Roberts
2006-06-11 19:27                     ` Eli Zaretskii
2006-06-11 21:42                       ` Nick Roberts
2006-06-12  3:36                         ` Eli Zaretskii
2006-06-12  6:19                           ` Nick Roberts
2006-06-13  3:39                             ` Eli Zaretskii
2006-06-13  4:46                               ` Nick Roberts
2006-06-13 17:26                                 ` Eli Zaretskii
2006-06-13 21:15                                   ` Nick Roberts
2006-06-14 18:30                                     ` Eli Zaretskii
2006-06-14 21:05                                       ` Nick Roberts
2006-06-15  6:56                                         ` Eli Zaretskii
2006-06-30  2:13                                           ` Nick Roberts
2006-06-30 12:09                                             ` Eli Zaretskii
2006-06-30 14:12                                               ` 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=u3benet0j.fsf@gnu.org \
    --to=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