From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: george@gly.bris.ac.uk
Cc: gdb-patches@sources.redhat.com
Subject: Re: Proposed gdb patch
Date: Fri, 07 Jun 2002 06:55:00 -0000 [thread overview]
Message-ID: <4634-Fri07Jun2002165255+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <200206061710.SAA03206@xterm1.gly.bris.ac.uk> (george@gly.bris.ac.uk)
> Date: Thu, 6 Jun 2002 18:10:27 +0100
> From: "G. Helffrich" <george@gly.bris.ac.uk>
>
> Following previous comments, here is an updated version of the
> proposed patch to gdb 5.1.1 (28 May 2002) that adds functionality to the gdb
> command language. It implements the "edit" command featured in the Sun and
> SGI dbx, which invokes your favorite file editor on the active line of the
> program being debugged.
Thanks.
> + add_com ("edit", class_files, edit_command,
> + concat ("Edit specified file or function.\n\
> + With no argument, edits file containing most recent line listed.\n\
> + ", "\
> + Editing targets can be specified in these ways:\n\
> + FILE:LINENUM, to edit at that line in that file,\n\
> + FUNCTION, to edit at the beginning of that function,\n\
> + FILE:FUNCTION, to distinguish among like-named static functions.\n\
> + *ADDRESS, to edit at the line containing that address.\n\
> + Uses EDITOR environment variable contents as editor (or ex as default).",NULL));
I'd prefer that this command used the location_completer as its
completion function, since the arguments it accepts are source code
locations similar to the "break" command.
> Index: gdb-5.1.1/src/gdb/doc/gdb.texinfo
The docs changes are approved, but please fix the following minor
problem:
> + @node Edit
> + @section Editing source files
Please add here an index entry, for example:
@cindex editing source files
next prev parent reply other threads:[~2002-06-07 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 10:10 G. Helffrich
2002-06-07 6:55 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-02 4:31 G. Helffrich
2002-07-02 8:47 ` Eli Zaretskii
2002-05-28 5:15 G. Helffrich
2002-05-28 9:03 ` Daniel Jacobowitz
2002-05-28 11:41 ` 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=4634-Fri07Jun2002165255+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=george@gly.bris.ac.uk \
/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