-
Notifications
You must be signed in to change notification settings - Fork 301
Feature Request: Ability to disable autocomplete #320
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
Comments
I'd like to second this request. Loving inky so far but this is the one thing that's been annoying me since I started using it. Thanks |
I'd like to third this request please. The style of brevity quest requires minimal punctuation, and having to hit Esc at the end of every line got very old, very fast. |
To those looking for a build with autocompletee disabled, setting enableLiveAutocompletion to false (line 26 of editorView.js in app/renderer) did the trick for me. |
First time user of inky ending up here after 5 minutes of usage, thinking "Wow, this experience is going to be rough because of this autocomplete feature. Where's the preferences menu to turn this off?" Google pointed me here. |
Wanted to add that I would appreciate this option! It can be handy (being able to tab to complete knot names and whatnot) but I typed "0" and it autocompleted to "101" and "c" completed to "continue" (as some examples) which can be frustrating to deal with. |
This didn't work for me, and I'm finding inky pretty dealbreakingly unusable for the same reasons already cited here. |
Thanks a million, @joethephish ! And thanks to everyone at inkle for providing such a useful tool for our use. |
Suggestion
Add either a simple on-off toggle to the Autocomplete feature, or else a modular one that allows for selective autocomplete of any of vocabulary, variables, and divert targets.
Access to the dictionary of words the project has built up - similar to how Openoffice handles it, allowing removal of individual entries and disabling of adding new words to the list - would be an even better feature, but I expect this would be harder to implement than simple category toggles.
Reasoning
Screenshot 1



Screenshot 2
Screenshot 3
The text was updated successfully, but these errors were encountered: