You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I appreciate the update to allow auto-complete to be disabled. In my case though, I find it overshoots the useful 'sweet spot'. Most of the time when I'm typing, I don't mind auto-complete. The times when it becomes bothersome for me are when adding tags (which I do all the time), and it tries to correct my tags to words used in the text. Despite it correcting a tag, it doesn't seem to recognise existing tags as words in its dictionary. Often I will type out a tag, press enter to go to the next line, and find the tag is replaced. However, auto-complete is really useful for adding functions, knots and other logical/syntactical elements, so I don't want to disable it completely.
I don't know how many people have similar frustrations but I imagine it's fairly common for anyone using tags. Some ideas for fixing this:
Allow auto-complete to be enabled for knots, function names, and anywhere else where typing it incorrectly will result in an error. But disable auto-complete for any freeform text that will compile regardless of what I type.
Don't confirm auto-complete suggestion when I press enter, but only when I press tab. Tab already works, but having enter as well just overrides the line return behaviour which I find intrusive.
I'm curious to know if anyone else has felt this. I realise others may be totally fine with this and recognise it isn't necessarily ideal to pack this application full of tiny little settings like these. Still, for me it would make a significant difference. In the meantime, I will have to train myself to press spacebar at the end of my tags before enter to break off the auto-complete (and to feel okay about the extra space character hanging off the end of my lines).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I appreciate the update to allow auto-complete to be disabled. In my case though, I find it overshoots the useful 'sweet spot'. Most of the time when I'm typing, I don't mind auto-complete. The times when it becomes bothersome for me are when adding tags (which I do all the time), and it tries to correct my tags to words used in the text. Despite it correcting a tag, it doesn't seem to recognise existing tags as words in its dictionary. Often I will type out a tag, press enter to go to the next line, and find the tag is replaced. However, auto-complete is really useful for adding functions, knots and other logical/syntactical elements, so I don't want to disable it completely.
I don't know how many people have similar frustrations but I imagine it's fairly common for anyone using tags. Some ideas for fixing this:
I'm curious to know if anyone else has felt this. I realise others may be totally fine with this and recognise it isn't necessarily ideal to pack this application full of tiny little settings like these. Still, for me it would make a significant difference. In the meantime, I will have to train myself to press spacebar at the end of my tags before enter to break off the auto-complete (and to feel okay about the extra space character hanging off the end of my lines).
Beta Was this translation helpful? Give feedback.
All reactions