Skip to content

counsel-M-x populates history for the execute-extended-command #1185

@mookid

Description

@mookid

On a setup that uses both counsel-M-x and execute-extended-command, the history becomes hard to use.

For instance:
M-x counsel-M-x
input "^cou git"
select the candidate counsel-git
later,
M-x
M-p

Here I get the previously entered string in the history, which is not really that helpful.

I see two possible improvements:

  • keep a separate history for the replacement command
  • keep a separate history and put the selected candidate in the history of the original command

What do you think about this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions