[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: |
Tue, 23 Aug 2022 12:27:19 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
I've now reverted these changes, because they just don't work well
enough. As I said in the commit message:
2022-08-23 Lars Ingebrigtsen <larsi@gnus.org>
* lisp/emacs-lisp/lisp-mode.el (lisp-current-defun-name): Revert
back to the old version before bug#49592. The new approach just
doesn't work well enough -- we don't really have the data to know
that, say, `make-obsolete-variable' is about the second symbol and
not the first.
So another approach is needed here.
- 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/04
- bug#49592: 28.0.50; lisp-current-defun-name and non-standard defuns, Lars Ingebrigtsen, 2022/08/05
- 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 <=
- 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, 2022/08/24