all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 59605@debbugs.gnu.org
Subject: bug#59605: 29.0.50; gdb no more creates Gud menu entry for source file window
Date: Sat, 26 Nov 2022 19:02:42 +0200	[thread overview]
Message-ID: <837czhsl71.fsf@gnu.org> (raw)
In-Reply-To: <53e5eea9-0550-af08-bc73-6918aa3f912e@gmx.at> (message from martin rudalics on Sat, 26 Nov 2022 11:28:28 +0100)

> Date: Sat, 26 Nov 2022 11:28:28 +0100
> From: martin rudalics <rudalics@gmx.at>
> 
> With emacs -Q visit an arbitrary Emacs C source file and do your
> equivalent of M-: (gdb "gdb -i=mi emacs").  Now selecting the window
> showing the source file buffer no more shows a Gud menu entry.  This has
> the consequence that mouse clicking in a fringe no more sets/unsets a
> breakpoint in that buffer.
> 
> The commit responsible for that behavior is
> 
> commit 8bb5c1bfec0929f2ba419e1c503f5acc01c336c2
> Author: Lars Ingebrigtsen <larsi@gnus.org>
> Date:   Thu Sep 1 13:39:14 2022 +0200
> 
>      Make easy-mmode-defmap obsolete and adjust only caller
> 
>      * lisp/emacs-lisp/easy-mmode.el (easy-mmode-defmap): Make obsolete.
>      * lisp/progmodes/gud.el (gud-menu-map): Use easy-menu-define.

Stefan, can you help here?  It looks like gud-minor-mode is not a proper
minor mode, so the new code isn't working because gud-minor-mode-map is not
in effect or something?





  reply	other threads:[~2022-11-26 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 10:28 bug#59605: 29.0.50; gdb no more creates Gud menu entry for source file window martin rudalics
2022-11-26 17:02 ` Eli Zaretskii [this message]
2022-11-28 17:55   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-28 19:21     ` Eli Zaretskii

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=837czhsl71.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59605@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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.