Open Brittany-Reid opened 4 years ago
The default keybindings are currently set for windows, but can be changed in a user's config.json. It would be nice, maybe when everything is done, to also have OS based defaults. I have added the functionality for OS dependant defaults, I would just need to know what keys should be different on linux and mac. I am happy for anyone on linux/mac to make changes to config.js, or to open issues for additional keys to be registered, but if it is not affecting core functionality (I cannot do x functionality on this OS), it is low priority. See #21 for some discussion on this.
This is an issue for general UI improvement to be done before release. These are low priority, as we need a functioning tool first, but also because we want to make sure we have systems built for the core features, then convenience UI features later.
Improved Suggestions
The current autocomplete is incredibly simple at the moment, and starts at the user's cursor when they press tab. There are a lot of custom rules we can add for autocompletes to determine when they should display. This could get complicated, so I'd like to make sure the task suggestions are intuitive first, then improve things like command suggestions.
Here is an example of what happens when a user wants suggestions after they start typing:
The improved suggestions would take previous input into account. We need to be careful about this though, as sometimes a user may want to do new suggestions, say
repl(<package>)
, looking for a package. We can see that they already have a function and provide suggestions for arguments to that function (in this case packages).Edit: I am also going to broaden this to general user experience improvements as well.