From: Claus Fischer <claus.fischer@clausfischer.com>
To: 30044@debbugs.gnu.org
Subject: bug#30044: Emacs: Gud-mode: Debugging with gud: Window switching problem
Date: Tue, 9 Jan 2018 13:33:11 +0100 [thread overview]
Message-ID: <20180109123311.klciuvflkdgm23pf@clausfischer.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Package: emacs
Version: all recent
Dear Emacs maintainers!
A few years ago, I filed a bug about debugging unter Emacs with
gud and gdb.
The problem is that often times when a halt at a breakpoint requires
a source file to load, the source file replaces the *gud-something*
buffer, which is extremely disruptive to the work flow. One expects
to continue typing in gud but finds oneself instead typing into some
source file buffer.
After more careful observation, I think that this problem occurs
especially when there's another * buffer, particularly the
*compilation* buffer, present.
This often occurs in my work setting: I fix a bug by editing the file,
I let emacs recompile (run make), I load the new binary into the
debugger and run it again.
Please forward this information to the gud-mode maintainers,
it might be helpful, and it might help many people who find this
behaviour quite disturbing.
Best regards
Claus
--
Claus Fischer <claus.fischer@clausfischer.com>
http://www.clausfischer.com/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2018-01-09 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:33 Claus Fischer [this message]
2018-01-09 18:44 ` bug#30044: Emacs: Gud-mode: Debugging with gud: Window switching problem Eli Zaretskii
2018-01-09 20:58 ` Claus Fischer
2018-01-10 3:28 ` Eli Zaretskii
2018-01-10 3:39 ` Noam Postavsky
2018-01-10 11:19 ` Claus Fischer
2018-01-11 1:58 ` Noam Postavsky
2018-01-11 13:24 ` Claus Fischer
2018-01-12 1:24 ` Noam Postavsky
2018-05-20 23:52 ` Noam Postavsky
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=20180109123311.klciuvflkdgm23pf@clausfischer.com \
--to=claus.fischer@clausfischer.com \
--cc=30044@debbugs.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.
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.