all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 49592@debbugs.gnu.org
Subject: bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns
Date: Wed, 24 Aug 2022 12:23:36 +0200	[thread overview]
Message-ID: <87fshmos7r.fsf@gnus.org> (raw)
In-Reply-To: <87bksain4m.fsf@web.de> (Michael Heerdegen's message of "Wed, 24 Aug 2022 00:57:45 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Is that because of `make-obsolete-variable's (indent defun) spec?  (And
> is that even appropriate?)
>
> Did you see examples where the edebug spec based mechanism you added
> failed?  Or maybe only this part:
>
>   (and (eq (get symbol 'lisp-indent-function) 'defun)
>        (get 'defun 'edebug-form-spec))
>
> was inappropriate?

The problem wasn't just with this function -- it turns out that we have
quite a few things that are used as top-level defining constructs that
aren't marked in any special way.  The old heuristics (i.e., "just use
the second bit in the form") handle these correctly.

But that means that I have no ideas for a practical way to fix the issue
this was supposed to fix -- i.e., top-level

(progn
  ;; 
  (foo-bar)
  ...)

and such.





      reply	other threads:[~2022-08-24 10:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16  2:53 bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns Michael Heerdegen
2022-08-04 16:31 ` Lars Ingebrigtsen
2022-08-05  2:11   ` Michael Heerdegen
2022-08-05  3:01     ` Michael Heerdegen
2022-08-05 11:57     ` Lars Ingebrigtsen
2022-08-06  0:17       ` Michael Heerdegen
2022-08-06 12:15         ` Lars Ingebrigtsen
2022-08-07  2:09           ` Michael Heerdegen
2022-08-08 12:32             ` Lars Ingebrigtsen
2022-08-09  2:12               ` Michael Heerdegen
2022-08-09 15:29                 ` Lars Ingebrigtsen
2022-08-12  5:28                   ` Michael Heerdegen
2022-08-12 15:06                     ` Lars Ingebrigtsen
2022-08-23 10:27                       ` Lars Ingebrigtsen
2022-08-23 22:57                         ` Michael Heerdegen
2022-08-24 10:23                           ` Lars Ingebrigtsen [this message]

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=87fshmos7r.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=49592@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.