From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add "fin" alias for "finish"
Date: Wed, 21 May 2008 19:44:00 -0000 [thread overview]
Message-ID: <uprrfh95w.fsf@gnu.org> (raw)
In-Reply-To: <20080521045022.GE4080@adacore.com>
> Date: Tue, 20 May 2008 21:50:22 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> And the associated doc update (Hello Eli! :):
>
> 2008-05-20 Joel Brobecker <brobecker@adacore.com>
>
> * gdb.texinfo (Continuing and Stepping): Document the new "fin"
> abbreviation for "finish".
Thanks.
> @kindex finish
> +@kindex fin @r{(@code{finish})}
> @item finish
> Continue running until just after function in the selected stack frame
> -returns. Print the returned value (if any).
> +returns. Print the returned value (if any). This command is abbreviated
> +@code{fin}.
I suggest to say "This command can be abbreviated as @code{fin}."
instead of the last sentence.
Other than that, the patch for the manual is okay.
next prev parent reply other threads:[~2008-05-21 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 15:26 Joel Brobecker
2008-05-21 19:44 ` Eli Zaretskii [this message]
2008-05-21 20:38 ` Joel Brobecker
2008-05-21 19:58 ` Daniel Jacobowitz
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=uprrfh95w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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