[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: |
Tue, 07 Jun 2022 16:15:47 +0300 |
> Cc: 45333@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 07 Jun 2022 13:57:36 +0200
>
> novim <laszlomail@protonmail.com> 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 going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> 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
...