bug#45333: complex command history should not save optional nil parameters

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: laszlomail@protonmail.com,  45333@debbugs.gnu.org
> Date: Thu, 09 Jun 2022 12:22:52 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> (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.
> 
> The advantage would be that the history is easier to navigate, because
> you don't have to stare at all those nils when going through the list
> looking for the command to execute.

OTOH, you get to see all the optional arguments, which is also useful.

It's a minor issue, to be sure.