Bug 431008 - Find without moving focus to one found
Summary: Find without moving focus to one found
Status: RESOLVED INTENTIONAL
Alias: None
Product: frameworks-ktexteditor
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-31 15:01 UTC by Piotr Mierzwinski
Modified: 2021-01-06 21:31 UTC (History)
2 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 Piotr Mierzwinski 2020-12-31 15:01:33 UTC
SUMMARY
Sometime user needs to find out if any string occurs in text and don't want to move focus (cursor) to place where this string occurs.

STEPS TO REPRODUCE
1. Open any longer text document in Kate or Kwrite
2. Try to find string which occurs at end of document (Ctrl+F)
3. 

OBSERVED RESULT
Focus is moving to place where string occurs

EXPECTED RESULT
Focus could be not moved to place where string occurs, only this would happen after pressing arrow down/up.
Alternatively user could get message like: "finding string appears X times in your document".

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: YES
(available in About System)
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Dominik Haumann 2021-01-01 14:16:30 UTC
If we add options for things like this, I believe we will end up with just too many options. Personally, I think this functions as designed, as users usually do want to jump to the searched location. So imho this is a not a bug and should be closed.
Comment 2 Piotr Mierzwinski 2021-01-04 23:19:55 UTC
This option no need to be available in bottom bar which appears after user involves searching. In my opinion this behavior might be set in Configuration.

> I think this functions as designed, as users usually do want to jump to the
> searched location.
I suppose this is happen often than situation when user wants only check if given string occurs in some document. 

But let imagine such situation. User updates some document adding some records in front or at end this document and preventing duplication want to check if any string/title occurs already in document or not. Jumping through document from point where was found this string to original location is not nice experience.
I hope present situation clearly.

> So imho this is a not a bug and should be closed.
Yes of course this is not a bug. I marked this report as a wish, so... this is still only a wish.
Comment 3 Nate Graham 2021-01-05 02:17:14 UTC
I have to agree with Dominik, sorry. :)

But isn't cursor position undoable now? So you can hit Ctrl+z and jump back to where you were before.

You might also be able to support this niche use case using the embedded terminal panel or the "filter through command" functionality.
Comment 4 Piotr Mierzwinski 2021-01-06 21:31:27 UTC
(In reply to Nate Graham from comment #3)
> I have to agree with Dominik, sorry. :)
> 
> But isn't cursor position undoable now? 
> So you can hit Ctrl+z and jump back to where you were before.
No isn't "undoable". Just try to do simple test, but don't edit document.

BTW. In Kate are available some scripts and among other there are: "go to next edit point" or "go to previous edit point". Only needs to assign some shortcuts for them. I think this will don't work if I will don't edit dokument.

> You might also be able to support this niche use case using the embedded
> terminal panel or the "filter through command" functionality.
Yes. I can open embedded terminal and grep document.

"filter through command".
This plugin is very limited and no so much useful. Yes it filtering document, only the problem is what this plugin doing with result. Are available two options:
- paste result in the same document, removing all what was selected
- copy to clipboard, so if I need to find 10 strings I need to open clipboard every time. I wonder why this plugin doesn't open new tab in editor pasting there result like does similar plugin in Notepad++.

Yes. This was niche use case for proposed function. Maybe doesn't make sense to add this.