unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: which-func.el unconditionally requiring edebug
Date: Fri, 25 Nov 2022 19:44:28 +0100	[thread overview]
Message-ID: <CAAeL0SSHAuqA-HQ4Sd=qYeB30=SKHE6jgfyBTju-siox1XoF3g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 817 bytes --]

Lars, would it be possible to delay (require 'edebug) until
lisp-current-defun-name is going to be used?

  commit 55cc8b040b0e3c5f97fd1386d1e9c5a120be6340
  Author: Lars Ingebrigtsen <larsi@gnus.org>
  Date:   2022-08-08 14:31:54 +0200

      Make which-func-mode output less junk

      * lisp/emacs-lisp/lisp-mode.el (lisp-current-defun-name): Use
      edebug specs to find the name (if they exist), and default to
      returning the top-level symbol if there isn't a define-like form
      (bug#49592).

I've spent quite a while trying to understand why

(setq edebug-inhibit-emacs-lisp-mode-bindings t)

was not working, turns out that I have

(eval-when-compile (require 'which-fun))

early in my .emacs and I certainly wasn't expecting it to affect edebug.
The change isn't even mentioned in the commit log.

[-- Attachment #2: Type: text/html, Size: 1837 bytes --]

             reply	other threads:[~2022-11-25 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 18:44 Juanma Barranquero [this message]
2022-12-07 15:17 ` which-func.el unconditionally requiring edebug Eli Zaretskii
2022-12-07 15:46   ` Juanma Barranquero
2022-12-07 18:09     ` Juanma Barranquero
2022-12-07 18:17       ` Eli Zaretskii
2022-12-07 21:28         ` Juanma Barranquero
2022-12-08  6:11           ` 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

  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='CAAeL0SSHAuqA-HQ4Sd=qYeB30=SKHE6jgfyBTju-siox1XoF3g@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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 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).