Repository navigation
Feature Request: Ability to disable autocomplete #320
Description
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
- Selective enable/disable of vocab, variables, and divert targets already possible via commenting out existing code, but not very user-friendly to do this method.
- Current autocomplete semi-frequently has false positives on common words (screenshots 1 and 2)
- Inclusion of a long string for whatever reason (dramatic effect of not using spaces, representation of encoded data, someone says the alphabet) then permanently becomes a false positive match for words (screenshot 3)
- When typing a script quickly, hitting enter to create a new line and accidentally replacing the last word with a diferent one - most noticeable with # tags, but also possible if the writer isn't using punctuation at the end of a line - gets frustrating very quickly.
- Also unsure how useful or not the Autocomplete feature is for non-english writers.
Screenshot 1
Screenshot 2
Screenshot 3
Reacted by Jackie M
Activity
jimthurston commentedon Apr 16, 2021
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
potatocubed commentedon Jul 9, 2021
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.
iluminacos commentedon Feb 27, 2023
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.
Alternatively, you can set this.exactMatch to true (line 1296 of ext-language_tools.js in app/renderer/acesrc). It keeps the feature, but makes it way less intrusive.
heyacfox commentedon Apr 22, 2023
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.
jnmccla commentedon Nov 14, 2023
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.
larryboyko commentedon Jun 13, 2024
This didn't work for me, and I'm finding inky pretty dealbreakingly unusable for the same reasons already cited here.
joethephish commentedon Jun 17, 2024
Okay added an option in e352083, and set
exactMatchto true in 1e29051. Thanks for the suggestions, folks!larryboyko commentedon Jun 17, 2024
Thanks a million, @joethephish ! And thanks to everyone at inkle for providing such a useful tool for our use.