From: Doug Evans <dje@google.com>
To: tromey@redhat.com
Cc: Joel Brobecker <brobecker@adacore.com>,
Pedro Alves <pedro@codesourcery.com>,
Marc Khouzam <marc.khouzam@ericsson.com>,
gdb@sourceware.org
Subject: Re: More descriptive prompt
Date: Wed, 25 Feb 2009 19:00:00 -0000 [thread overview]
Message-ID: <e394668d0902251100k31c5aeb2kbb643a92c76b2f67@mail.gmail.com> (raw)
In-Reply-To: <m3prh6gxmb.fsf@fleche.redhat.com>
On Wed, Feb 25, 2009 at 10:49 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>
>>> This is what I was using at one point. It added a PS1 style
>>> formatting to the gdb command, so I could do
>>>
>>> (gdb) set prompt (\\p \\T: \\S)
>
> Joel> Sounds like a useful idea to me. I'm torn between a python approach
> Joel> and Pedro's approach. Pedro's approach might be seen as less powerful,
> Joel> since one cannot extend the list of available escape sequences without
> Joel> rebuilding GDB. But I think it has the advantage of being simple
> Joel> to implement and simple to use.
>
> One could also write a Python hook, and then implement the PS1-style
> substitution idea in Python :-)
Ya, ya, that occurred to me. :-)
fwiw, I'd prefer to support a more intelligent prompt without requiring python.
But I'm happy to implement whatever y'all agree on.
next prev parent reply other threads:[~2009-02-25 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 18:12 More descriptive prompt [was Re: Process exit in multi-process, and gdb's selected thread.] Doug Evans
2009-02-24 18:26 ` Daniel Jacobowitz
2009-02-24 18:41 ` Pedro Alves
2009-02-24 19:09 ` Pedro Alves
2009-02-25 17:41 ` Joel Brobecker
2009-02-25 17:49 ` Doug Evans
2009-02-25 17:59 ` Paul Pluzhnikov
2009-02-25 18:52 ` More descriptive prompt Tom Tromey
2009-02-25 19:00 ` Doug Evans [this message]
2009-02-25 19:42 ` Tom Tromey
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=e394668d0902251100k31c5aeb2kbb643a92c76b2f67@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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