From: Z <zhushenli@gmail.com>
To: help-gnu-emacs@gnu.org
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to render gud (python debugger) output?
Date: Fri, 5 Oct 2012 17:29:30 -0700 (PDT) [thread overview]
Message-ID: <e5b8da66-f9a5-4f87-b230-c30108aad3a3@googlegroups.com> (raw)
In-Reply-To: <mailman.10336.1349426401.855.help-gnu-emacs@gnu.org>
On Friday, October 5, 2012 4:40:03 PM UTC+8, Eli Zaretskii wrote:
> > Date: Fri, 5 Oct 2012 01:30:19 -0700 (PDT)
>
> > From: Z <zhushenli@gmail.com>
>
> > Injection-Date: Fri, 05 Oct 2012 08:30:19 +0000
>
> >
>
> > I use gud pdb to debug Python program. But output of gud is mono color
>
> > and hard to identify the information in a huge chuck of
>
> > output(e.g. type "bt" and find current frame in stack). So I want to add color and link to the output.
>
> >
>
> > How to render gud output? What function shall I add or change?
>
>
>
> Did you try the command below?
>
>
>
> M-x gdb-many-windows RET
>
>
>
> You can also invoke it by clicking "Gud->GDB-MI->Display Other Windows"
>
> from the menu bar.
>
>
>
> This causes the call stack be automatically displayed in a separate
>
> window, with clickable frames. So you should not need to examine the
>
> output of "bt" manually, if you don't want to.
Eli, thank you.
I prefer command line debug without so many windows open. Besides, gdb-many-windows() seems not callable in gud-pdb mode, maybe it's only available in gud-gdb mode.
And I have gone through gud code and found supports for other debuggers except gdb are rudimentary. So I add the code to .emacs to highlight/hide python debugger outputs.
(add-hook 'pdb-mode-hook
(lambda ()
(progn
(hi-lock-face-buffer "^-> +.+$\\|^.+pdb\\.py.+$\\|^.+bdb\\.py.+$" 'org-hide)
(hi-lock-face-buffer "^> [-a-zA-Z0-9_/.:\\]*([0-9]+)" 'bold)
)))
prev parent reply other threads:[~2012-10-06 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 8:30 How to render gud (python debugger) output? Z
2012-10-05 8:40 ` Eli Zaretskii
[not found] ` <mailman.10336.1349426401.855.help-gnu-emacs@gnu.org>
2012-10-06 0:29 ` Z [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5b8da66-f9a5-4f87-b230-c30108aad3a3@googlegroups.com \
--to=zhushenli@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).