From: Eli Zaretskii <eliz@gnu.org>
To: Devon Sean McCullough <Emacs-Hacker2020@jovi.net>
Cc: 53193@debbugs.gnu.org
Subject: bug#53193: 29.0.50; gud bombs
Date: Tue, 11 Jan 2022 22:14:55 +0200 [thread overview]
Message-ID: <83bl0i6ncw.fsf@gnu.org> (raw)
In-Reply-To: <718fcd08-f500-8b4c-80f6-80fa81f91524@jovi.net> (message from Devon Sean McCullough on Tue, 11 Jan 2022 14:24:21 -0500)
> Date: Tue, 11 Jan 2022 14:24:21 -0500
> From: Devon Sean McCullough <Emacs-Hacker2020@jovi.net>
>
> (defun gud-tooltip-tips …
> (cons 'and gud-tooltip-display)
>
> ;; should be more like
>
> (defun gud-tooltip-tips …
> (cons 'and (mapcar (lambda (form)
> (list 'ignore-errors form))
> gud-tooltip-display))
>
> ;; a workaround is
>
> (setq gud-tooltip-display
> '((and gud-overlay-arrow-position
> (eq (tooltip-event-buffer gud-tooltip-event)
> (marker-buffer gud-overlay-arrow-position)))))
Could you please show the minimal recipe for reproducing the problem?
> ;; P.S. Should gud be fixed or flushed in favor of realgud?
It is basically deprecated in favor of gdb-mi. But some people still
prefer gud.el.
> ;; P.P.S. Should gud-lldb.el be incorporated into gud?
No, we don't want to develop gud.el, we want to develop gdb-mi.el
instead. So if LLDB developers get their act together and provide
decent support for the GDB/MI interface, LLDB users could simply use
the existing gdb-mi.el.
next prev parent reply other threads:[~2022-01-11 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 19:24 bug#53193: 29.0.50; gud bombs Devon Sean McCullough
2022-01-11 20:14 ` Eli Zaretskii [this message]
2022-02-10 8:45 ` Lars Ingebrigtsen
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=83bl0i6ncw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53193@debbugs.gnu.org \
--cc=Emacs-Hacker2020@jovi.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).