From: Xin Jin <zariskij@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: highlight breakpoints with pdb?
Date: Tue, 18 Nov 2014 14:29:09 -0800 (PST) [thread overview]
Message-ID: <ecf125c6-3caf-4b33-a9f1-c8904b764804@googlegroups.com> (raw)
I use pdb with gud to debug python scripts. I am just wondering if there is way to highlight the lines with breakpoints? For example, in some screenshots of gud-gdb, some people seem to have red circles to the left of lines with breakpoints. How to achieve that with pdb? And is there a way to list all breakpoints (like the breakpoints buffer of gud-gdb)?
I actually tried realgud once, and it did have this feature. However, realgud is lacking documentation, and I find it extremely confusing to use. I have very limited knowledge of elisp, so I cannot figure out what is going on without a more detailed guide.
Thanks.
next reply other threads:[~2014-11-18 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 22:29 Xin Jin [this message]
2014-11-19 7:01 ` highlight breakpoints with pdb? Andreas Röhler
[not found] ` <mailman.13998.1416380496.1147.help-gnu-emacs@gnu.org>
2014-11-19 9:17 ` Xin Jin
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=ecf125c6-3caf-4b33-a9f1-c8904b764804@googlegroups.com \
--to=zariskij@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).