From: Yuri Khan <yuri.v.khan@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 18294@debbugs.gnu.org
Subject: bug#18294: 24.3; gud and/or gdb: Add hooks to detect when a source file is visited during debugging
Date: Sun, 24 Aug 2014 17:32:58 +0700 [thread overview]
Message-ID: <CAP_d_8W6S2836tH2drp_Qy-=vqWK9=vLx6ZMbr=N3v7GN_TiRA@mail.gmail.com> (raw)
In-Reply-To: <53F5BACB.3060804@gmx.at>
On Thu, Aug 21, 2014 at 4:24 PM, martin rudalics <rudalics@gmx.at> wrote:
>
> I'd like such a thing. But wouldn't it be easier to do this right in
> gdb-mi.el? All I'd need is a simple key combination to toggle this
> behavior off whenever I want to modify code on the fly. The next "run"
> would then turn the behavior on again.
“This behavior” consists of two changes to the current state (which
allows editing while debugging):
* binding additional keys, and
* locking source files to be read-only,
and these changes need to be done simultaneously.
This may be achieved several ways, one of them being a minor mode,
which I am suggesting here.
Other ways include:
* Binding keys directly in the gud-minor-mode-map, along with fringe
clicks. This way, each such binding will have to check for a flag
(which may or may not be the read-only flag), and invoke either the
appropriate debugger command or self-insert-command.
* Binding keys globally, then checking if the debugger is active, in
addition to the above.
In my opinion, a separate minor mode is much cleaner than any of the
latter options.
next prev parent reply other threads:[~2014-08-24 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 4:59 bug#18294: 24.3; gud and/or gdb: Add hooks to detect when a source file is visited during debugging Yuri Khan
2014-08-21 9:24 ` martin rudalics
2014-08-24 10:32 ` Yuri Khan [this message]
2014-08-29 8:59 ` martin rudalics
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='CAP_d_8W6S2836tH2drp_Qy-=vqWK9=vLx6ZMbr=N3v7GN_TiRA@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=18294@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.