From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, bauerman@br.ibm.com, msnyder@vmware.com
Subject: Re: [RFA] Resubmit reverse debugging [5/5]
Date: Thu, 09 Oct 2008 08:41:00 -0000 [thread overview]
Message-ID: <u4p3mjh54.fsf@gnu.org> (raw)
In-Reply-To: <200810090522.43534.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Thu, 9 Oct 2008 05:22:43 +0100
> Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
> msnyder@vmware.com
>
> On Wednesday 08 October 2008 20:15:16, Eli Zaretskii wrote:
> > > From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> > > What about adding "previous" and either "pr" or "pre" as alias to
> > > reverse-next?
> >
> > Please, not "pr". The .gdbinit file that comes with Emacs defines a
> > user command named "pr" that prints any Lisp object. This command is
> > central to debugging Emacs, so re-learning its name would be a hassle.
>
> This argument isn't valid. User defined commands override
> GDB's built-in commands, so you'd not lose anything.
I know about the overriding, and I'm sorry for not making myself clear
about that (somehow, I thought it was obvious). My problem was not
with the technical aspects, but with human aspects. Like this, for
example:
> (gdb) pr
> Ambiguous command "pr": print, print-object, printf, process.
Exactly! Right now, if I forget that I'm not debugging Emacs (yes, it
happens ;-) and type "pr" out of habit, I get the above response, or
something similar. With the proposed alias, I might get the
`previous' command actually _executed_, to my surprise and annoyance.
Another problem is that I will lose the alias when I'm debugging
Emacs. Not good, IMO.
next prev parent reply other threads:[~2008-10-09 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 2:23 Michael Snyder
2008-10-08 18:15 ` Thiago Jung Bauermann
2008-10-08 19:16 ` Eli Zaretskii
2008-10-09 4:23 ` Pedro Alves
2008-10-09 8:41 ` Eli Zaretskii [this message]
2008-10-08 20:14 ` Thiago Jung Bauermann
2008-10-08 20:55 ` Michael Snyder
2008-10-08 20:27 ` Michael Snyder
2008-10-08 20:43 ` Thiago Jung Bauermann
2008-12-15 12:29 ` Tomas Holmberg
2008-10-08 21:06 ` Michael Snyder
2008-10-08 21:14 ` Thiago Jung Bauermann
2008-10-17 19:48 ` Michael Snyder
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=u4p3mjh54.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.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