[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns
From: |
Lars Ingebrigtsen |
Subject: |
bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns |
Date: |
Wed, 24 Aug 2022 12:23:36 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
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.
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, (continued)
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Michael Heerdegen, 2022/08/05
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Lars Ingebrigtsen, 2022/08/06
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Michael Heerdegen, 2022/08/06
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Lars Ingebrigtsen, 2022/08/08
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Michael Heerdegen, 2022/08/08
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Lars Ingebrigtsen, 2022/08/09
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Michael Heerdegen, 2022/08/12
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Lars Ingebrigtsen, 2022/08/12
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Lars Ingebrigtsen, 2022/08/23
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Michael Heerdegen, 2022/08/23
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns,
Lars Ingebrigtsen <=