Skip to content
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

Closed
JasonWoof opened this issue Apr 5, 2015 · 5 comments
Closed

Enter should not auto-complete commandline arguments #141

JasonWoof opened this issue Apr 5, 2015 · 5 comments

Comments

@JasonWoof
Copy link

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:

  1. auto-completing command names is awesome (since incomplete command names don't work).
  2. auto-completing command+parameters results in inconsistent (across time) results, thus forcing the user to break their concentration to pay attention to your program, instead of just typing what they want. It is important to me that I can always type the same sequence of keys to get a web browser. When this is the case, that sequence of keys becomes a habit, something I can do without breaking my concentration.
@DaveDavenport
Copy link
Collaborator

The problem described is caused by history. Disable history should make it be consistent.

If enabled, when you enter iceweasel someurl.com this will be added to history.

Next time you search icew: iceweasel and iceweasel someurl.com is in the list.

Depending on the sorting algorithm set, it will either pick closes match iceweasel (levensteihn) or iceweasel someurl.com (last used)

@JasonWoof
Copy link
Author

Thanks. Disabling history is good enough for me.

@gergesh
Copy link
Contributor

gergesh commented Jan 6, 2018

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?

@ghost
Copy link

ghost commented May 15, 2018

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.

@sardemff7
Copy link
Collaborator

It already exists, and it gets added to the history. Please do not revive ancient bug reports for unrelated (or loosely related) comments.

@davatorium davatorium locked as resolved and limited conversation to collaborators May 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants