[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#66979: Wrong number of arguments with completion-at-point
From: |
Stefan Monnier |
Subject: |
bug#66979: Wrong number of arguments with completion-at-point |
Date: |
Tue, 07 Nov 2023 19:02:28 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
> What has happened is that the advice macroexpand-advice in
> elisp--local-variables has been applied to macroexpand-1, and due to the
> typo there, never gets removed (now fixed with bug #65622). This piece
> of advice is what suppresses the backtrace.
Ah, right, so we're actually not inside `elisp--local-variables` any
more, it's just that the advice was left by error.
> But I think I added the debug to that condition-case handler before
> spotting and correcting the typo in macroexpand[-1]. So it may well be
> that that debug could be removed without great damage.
Exactly. Thanks,
Stefan
- bug#66979: Wrong number of arguments with completion-at-point, Juri Linkov, 2023/11/07
- bug#66979: Wrong number of arguments with completion-at-point, Juri Linkov, 2023/11/07
- bug#66979: Wrong number of arguments with completion-at-point, Stefan Monnier, 2023/11/07
- bug#66979: Wrong number of arguments with completion-at-point, Alan Mackenzie, 2023/11/07
- bug#66979: Wrong number of arguments with completion-at-point, Stefan Monnier, 2023/11/07
- bug#66979: Wrong number of arguments with completion-at-point, Alan Mackenzie, 2023/11/07
- bug#66979: Wrong number of arguments with completion-at-point,
Stefan Monnier <=
- bug#66979: Wrong number of arguments with completion-at-point, Juri Linkov, 2023/11/09
- bug#66979: Wrong number of arguments with completion-at-point, Stefan Monnier, 2023/11/12