From: Daniel Jacobowitz <drow@mvista.com>
To: "G. Helffrich" <george@gly.bris.ac.uk>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Proposed gdb patch
Date: Tue, 28 May 2002 09:03:00 -0000 [thread overview]
Message-ID: <20020528160300.GB12301@branoic.them.org> (raw)
In-Reply-To: <200205281057.LAA00860@xterm1.gly.bris.ac.uk>
On Tue, May 28, 2002 at 11:57:14AM +0100, G. Helffrich wrote:
>
> Dear GDBers -
>
> Here is a patch to gdb 5.1.1 that adds functionality to the gdb command
> language. It implements the "edit" command featured in Sun's dbx, which
> invokes your favorite file editor on the active line of the program being
> debugged. ChangeLog entry and patches follow.
>
> George
>
> ----------
>
> 2002-04-26 George Helffrich <george@gly.bris.ac.uk>
>
> * cli/cli-cmds.c, defs.h, source.c, gdb.1: Add edit command. This
> command mimics the behavior of Sun dbx, and invokes an editor at
> the current line number. Editor comes from EDITOR environment
> variable, or defaults to /bin/ex.
My bias is showing, but could you default to:
- vi rather than ex, since fullscreen edit support is far more
prevalent than not in this decade.
- Using $PATH, since I believe that neither BSDs nor Linuxen put
editors in /bin generally.
Oh, and again, you may want to update gdb.texinfo. That's the current
updated documentation.
Thanks for the patch!
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-28 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 5:15 G. Helffrich
2002-05-28 9:03 ` Daniel Jacobowitz [this message]
2002-05-28 11:41 ` Eli Zaretskii
2002-06-06 10:10 G. Helffrich
2002-06-07 6:55 ` Eli Zaretskii
2002-07-02 4:31 G. Helffrich
2002-07-02 8:47 ` 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=20020528160300.GB12301@branoic.them.org \
--to=drow@mvista.com \
--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