This is the mail archive of the
mailing list for the GDB project.
Re: [RFC/WIP PATCH 07/14] Expand %ITSET% in the prompt to the current I/T set.
- From: Pedro Alves <pedro at codesourcery dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 16 Dec 2011 19:33:06 +0000
- Subject: Re: [RFC/WIP PATCH 07/14] Expand %ITSET% in the prompt to the current I/T set.
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com>
On Friday 16 December 2011 19:06:47, Tom Tromey wrote:
> >>>>> "Pedro" == Pedro Alves <firstname.lastname@example.org> writes:
> Tom> I don't mind if you want to push some prompt stuff into the core, but I
> Tom> think it would be better if done in a way that was compatible with the
> Tom> Python prompt substitution code -- command-wise,
> Tom> substitution-style-wise, and whatever else.
> Pedro> I'm not certain about what you mean by this. The %%
> Pedro> sustitution added applies after the python substitution, basically
> Pedro> a sed before display. The result isn't stored anywhere.
> Pedro> The "only" thing affected AFAICS is that to print '%', we'd have
> Pedro> to escape it (e.g., %% => '%'), though I haven't implemented that.
> It just seems strange to me for set extended-prompt to use one syntax,
> but for this to use a different syntax. I realize consistency is not
> GDB's strong suit, but this goes too far :)
Oh, I was aware of gdb.prompt_hook, but I completely missed
"set extended-prompt". :-) And it looks like a just built gdb doesn't
pick up commands from $srcdir/gdb/python/lib/gdb/command/ . grep
found it though.