-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Autocompletion gets in the way #3522
Comments
@JabRef/developers As a fix I suggest to disable auto completion again by default. |
Huge step: Survey in the forum. Who uses autocompletion, how, ... Present edge cases, present solutions Currently no resources for that, so we disable the auto completion. |
What about adding a telemetry data point that tracks if user have autocompletion enabled or not? |
This has already been fixed with #3569, hence I am closing. |
@lenhard As much as I like closed issues, I think this one should stay open. The underlying problem is still not fixed and we only disabled the autocompletion feature by default....in the long term, I would really like to have a functional autocompletion that we are proud to present to the user. |
This issue doe not point to a lot of concrete problems tho. I think there are plenty of such issues open. This was just a general issue. |
Ok, if you think that the issues autocompletion are enough, then we can of course leave this closed (as I said, I love closed issues 😄 ). |
Dunno, maybe we could use an issue where all problems are collected, if someone wants to give the AC a try again. |
If i want to edit the text e.g., inside the title field of an entry and jump to the front via Pos1 key or so autocompletion totally screws up the navigation, even if I am inside the text.
For me this is totally unnerving. The way the autocompletion works right now is not a lot better than it was before we disabled the old one...
The text was updated successfully, but these errors were encountered: