https://bugs.kde.org/show_bug.cgi?id=316413
Ben Bucksch <linux.n...@bucksch.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linux.n...@bucksch.org
Ever confirmed|0 |1
Resolution|INTENTIONAL |---
Status|RESOLVED |REOPENED
--- Comment #6 from Ben Bucksch <linux.n...@bucksch.org> ---
This bug is probably the most infuriating misfeature of Kate. I love Kate and
use it for everything, and the autocomplete *is* very useful. But only on tab,
not on Enter.
This is made worse by the fact that it takes any word already in the document
as autocomplete candidate. That means, if anywhere in the document is the word
"kate", I can no longer type "k" on its on line, by typing "k[ENTER]". It will
always write "kate". What's most infuriating is that it's insisting on it. Even
if I correct it and delete "ate", leaving only "k" as I wanted, and press enter
to get to the new line, it will again autocomplete to "kate".
A text editor should write whatever I type, not something completely different.
An autocomplete must always be activated intentionally by the user and not
happen by itself.
What is useful is:
* k[TAB] -> kate
* k -> dropdown opens -> [ARROW DOWN][ENTER]
I need that autocomplete all the time. I cannot disable it.
What's buggy is:
* k[ENTER] -> kate\n
What's expected is:
* k[ENTER] -> k\n
That expected result shouldn't be too surprising, because that's exactly what I
typed, and a text editor needs to write what I type, and not something
completely different.
This is a bug.
If you insist that some people like the buggy behavior, then you can make a
pref. But please allow me to use the editor properly, and to use autocomplete
in a way that's useful and not interfering with normal typing.
--
You are receiving this mail because:
You are watching all bug changes.
