From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: gdba problems with C++ code
Date: Wed, 6 Sep 2006 22:20:02 +1200 [thread overview]
Message-ID: <17662.41170.40438.149274@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060906.105320.74732193.wl@gnu.org>
> It does, thanks. For the moment, I have only one remaining question
> which is probably not directly related to gdba: Using mouse-1 to open
> the tree leaves (for structures watched in the speedbar frame)
> sometimes fails. I have to click just once to open it, right? For
> me, this often doesn't work, and I have to click again on the icon to
> see a reaction. Have you ever seen such a problem? It looks like
> Emacs doesn't receive all mouse events, or that they get lost
> somewhere. I use the CVS from today on a GNU/Linux box, running X
> 6.9.0.
I don't think it's an Emacs problem. It doesn't happen if you are just
browsing files in the speedbar, right? I think it's because I've made
gdb-enqueue-input a no-op if GDB is still executing (gud-running is t) :
(defun gdb-enqueue-input (item)
(if (not gud-running)
^^^^^^^^^^^^^^^^
(if gdb-prompting
(progn
(gdb-send-item item)
(setq gdb-prompting nil))
(push item gdb-input-queue))))
You can get better response if you omit that clause but Emacs might get
confused at times. GDB/MI should make things easier with tokens to
tie GDB output to GDB input.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-09-06 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17661.62609.88044.965992@kahikatea.snap.net.nz>
[not found] ` <20060906.010820.92574304.wl@gnu.org>
[not found] ` <17662.14141.844975.205652@kahikatea.snap.net.nz>
2006-09-06 8:53 ` gdba problems with C++ code Werner LEMBERG
2006-09-06 10:20 ` Nick Roberts [this message]
2006-09-04 6:53 Werner LEMBERG
2006-09-04 21:22 ` Nick Roberts
2006-09-04 22:36 ` Werner LEMBERG
2006-09-05 3:30 ` Eli Zaretskii
2006-09-05 3:46 ` Nick Roberts
2006-09-05 5:34 ` Werner LEMBERG
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=17662.41170.40438.149274@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@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.