From: John Wiegley <johnw@gnu.org>
Subject: Could the new gud changes move to a branch?
Date: Fri, 09 Apr 2004 00:14:25 -0700 [thread overview]
Message-ID: <m2vfk9oc6m.fsf@Majnun.local> (raw)
I appreciate whoever is trying to make gud smarter, but unfortunately
is stumbling over its own feet far too often. It has nearly rendered
debugging from within Emacs impossible.
It is much slower to get started. It creates three windows, but
expects a certain arrangement, so that every once in a while when I
hit my breakpoint I am left with only the source window -- and must
hit C-x C-b to get back to the *gud* window.
I really like the new disassembly view, but at one point I got myself
into a situation where I simply could not switch my buffer away from
it. It seemed to take over my minibuffer or something, and I had to
kill the process and restart it.
And lastly it seems that if the input/output window goes away (from
hitting C-x 1), and then I switch to the *gud* window and hit "up" or
"down", that it redisplays my frame so that only the source window and
the input/output window are displayed. I have to keep switching to
the *gud* buffer.
Anyway, it has felt very complicated, and I used to be such a fan of
debugging with gdb under Emacs. So could we go back to the old,
simple way until things settle down and the new code is better tested
by the author? I think I will start using 21.3 for my debugging.
John
next reply other threads:[~2004-04-09 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 7:14 John Wiegley [this message]
2004-04-09 9:31 ` Could the new gud changes move to a branch? Nick Roberts
2004-04-09 15:52 ` Stefan Monnier
2004-04-11 2:35 ` Richard Stallman
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=m2vfk9oc6m.fsf@Majnun.local \
--to=johnw@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.