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
Enter should not auto-complete commandline arguments #141
Comments
The problem described is caused by history. Disable history should make it be consistent. If enabled, when you enter Next time you search Depending on the sorting algorithm set, it will either pick closes match |
Thanks. Disabling history is good enough for me. |
I know that this is old and closed - but I'd like to join the request. Disabling history isn't a good solution. I'd like to be able to type commands that require command line arguments without the compromise of typing 'ch' and being offered abcecho instead of chromium. Would it be hard to implement history only for the first word in the command? |
Another solution could be to introduce a key bind to run the command written by the user instead of the one suggested/auto-completed, so you don't have to delete an entry or disable history every time. |
It already exists, and it gets added to the history. Please do not revive ancient bug reports for unrelated (or loosely related) comments. |
This report is about -show run
Use-case:
I type: icew and press enter
result: it runs "iceweasel", as it should
I type: iceweasel jasonwoof.com
result: it opens my home page
I type: icew
result: it opens my home page
expected result: it opens iceweasel (not passing it any paramaters)
me: wtf? I didn't ask for jasonwoof.com, I just wanted iceweasel
Conclusions:
The text was updated successfully, but these errors were encountered: