New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
mookid opened this Issue Sep 6, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@mookid
Contributor

mookid commented Sep 6, 2017

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?

@abo-abo

This comment has been minimized.

Owner

abo-abo commented Sep 6, 2017

What do you think about this?

Doesn't using counsel-M-x imply you're using ivy-mode? In that case, ^cou git still works for execute-extended-command.

@mookid

This comment has been minimized.

Contributor

mookid commented Sep 6, 2017

I am not using ivy-mode, just binding a bunch of commands; I am interested in both behaviors.

@abo-abo abo-abo closed this in 7284ca6 Sep 6, 2017

@abo-abo

This comment has been minimized.

Owner

abo-abo commented Sep 6, 2017

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment