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

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> > I  often use complex command history and I often copy commands from it to 
>> > my
>> > notes. For some commands the expression saved in this history is
>> > more complex than
>> > necessary.
>> >
>> > Here's an example with a simple command:
>> >
>> > I do a query replace then go to complex command history which shows:

[...]

>> I'm unfamiliar with the term "complex command history" -- how do you see
>> this history?
>
> I think like this:
>
>   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?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no