We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On a setup that uses both counsel-M-x and execute-extended-command, the history becomes hard to use.
counsel-M-x
execute-extended-command
For instance: M-x counsel-M-x input "^cou git" select the candidate counsel-git later, M-x M-p
M-x counsel-M-x
counsel-git
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:
What do you think about this?
The text was updated successfully, but these errors were encountered:
Doesn't using counsel-M-x imply you're using ivy-mode? In that case, ^cou git still works for execute-extended-command.
ivy-mode
^cou git
Sorry, something went wrong.
I am not using ivy-mode, just binding a bunch of commands; I am interested in both behaviors.
7284ca6
Thanks.
No branches or pull requests
On a setup that uses both
counsel-M-x
andexecute-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:
What do you think about this?
The text was updated successfully, but these errors were encountered: