[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45333: complex command history should not save optional nil paramete
From: |
Eli Zaretskii |
Subject: |
bug#45333: complex command history should not save optional nil parameters |
Date: |
Wed, 08 Jun 2022 16:57:11 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: laszlomail@protonmail.com, 45333@debbugs.gnu.org
> Date: Wed, 08 Jun 2022 13:43:50 +0200
>
> > M-x repeat-complex-command RET
> > M-n
> > M-n
> > ...
>
> Ah; thanks. Yes, we land things like
>
> (replace-string "foo" "bar" nil nil nil nil nil)
>
> in `command-history' -- where all those nils are optional. We could
> pretty easily filter those out by looking at the signature of the
> function and peeling off trailing nils, I think? Would there be any
> disadvantages to doing so?
I don't see any advantages, FWIW.