Bug 381024 - Autocomplete back-searches word
Summary: Autocomplete back-searches word
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: 16.08
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-09 16:41 UTC by Charter
Modified: 2022-09-27 04:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charter 2017-06-09 16:41:24 UTC
It would be nice to turn off this new back-search i'm noticing on the autocomplete word feature. 
Say I have the following words in a document:
one
TOKEN_one
WIDGET_one

everytime I type "one" and press enter I'll get "TOKEN_one". It is driving me nuts, especially when writing documentation. It is also annoying when it comes to case sensitive words e.g. "Software" vs "software"
Comment 1 Christoph Cullmann 2018-08-17 20:27:26 UTC
Valid wish, patches welcome.
Comment 2 Lothar 2018-12-08 07:15:04 UTC
(In reply to Charter from comment #0)
> It would be nice to turn off this new back-search 

Here (Kate 18 something, but that should be there for much longer) can you disable that at the Config page. 

  Editing (left column) -> Auto Completition (Tab) -> General (Row)

> Say I have the following words in a document:
> one
> TOKEN_one
> WIDGET_one
> 
> everytime I type "one" and press enter I'll get "TOKEN_one". It is driving
> me nuts

In the beginning it was a little bit strange, but quikly I loved this feature. 
You have to ask you why you hit enter and not space. No substitution take effect this way.
Comment 3 Dominik Haumann 2020-02-01 09:18:46 UTC
There was a patch to change the behavior:
https://phabricator.kde.org/D22477

This patch was rejected for now, since the current behavior helps a lot to discover API.

Adding an option, this patch still could go in, but it seems this was not done.
Comment 4 Waqar Ahmed 2022-08-28 08:21:22 UTC
Is this still reproducible?
Comment 5 Bug Janitor Service 2022-09-12 04:36:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-09-27 04:48:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!