[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45333: complex command history should not save optional nil paramete
From: |
Stefan Monnier |
Subject: |
bug#45333: complex command history should not save optional nil parameters |
Date: |
Thu, 07 Jul 2022 09:58:29 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
>> OClosure or not doesn't make much of a difference here, I think (the
>> previous version of the code would also be quite hideous in C).
>> Why not just call `advice--cd*r`?
> Sure, that's possible, but just seems a bit backwards.
Don't know about backward, but if you don't like that dependency, you
could break it using a hook, like a `function-unwrap-function` whose
default value is `identity` and which `nadvice.el` could change to
`advice-cd*r`.
Stefan
- bug#45333: complex command history should not save optional nil parameters, (continued)
- bug#45333: complex command history should not save optional nil parameters, Stefan Monnier, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters, Lars Ingebrigtsen, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters, Stefan Monnier, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters, Lars Ingebrigtsen, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters, Stefan Monnier, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters, Lars Ingebrigtsen, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters, Stefan Monnier, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters, Lars Ingebrigtsen, 2022/07/07
- bug#45333: complex command history should not save optional nil parameters,
Stefan Monnier <=
- bug#45333: complex command history should not save optional nil parameters, Drew Adams, 2022/07/05