This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Redefining built-in commands.
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- To: dhoward at redhat dot com
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 31 May 2002 10:22:22 +0300
- Subject: Re: Redefining built-in commands.
- References: <Pine.LNX.4.33.0205301449040.8589-100000@theotherone>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Thu, 30 May 2002 17:24:05 -0700 (PDT)
> From: Don Howard <dhoward@redhat.com>
>
> Should gdb allow users to redefine built-in commands?
I think it should, unless we cannot do it safely.
> If so, should the
> orignial alias continue to behave like the original built-in, or should
> it's behavior be modified also?
I'm not 100% sure, but I tend to think the aliases that are mere
abbreviations, like `n' for `next', should be redefined to the new
command, while aliases which aren't abbreviations should be left to
point to the original command.
But if the above cannot be done, we should either redefine the aliases
to the new command, or disable the aliases entirely. Crashing is not
an option, obviously.