Bug 471463 - Request: "whole word" button in Kate Ctrl+Shift+F search panel
Summary: Request: "whole word" button in Kate Ctrl+Shift+F search panel
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: search (show other bugs)
Version: 23.04.2
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-26 10:26 UTC by Quinten Kock
Modified: 2024-07-30 03:46 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 Quinten Kock 2023-06-26 10:26:05 UTC
SUMMARY
In the Kate search panel, there are currently options to "Match case" and "Enable regular expressions".
Additionally, in the Kate Ctrl-F bar, there's a button for Match case.
It would be nice to add a way to easily filter matches by whole word (VSCode for example supports this, and in ripgrep you can use the -w parameter for this).
I believe this can also be achieved by using regex word boundaries, but a GUI button is easier to use for most users.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
There was a request for this in Ctrl-F before: bug 290010. However that does not cover Ctrl+Shift+F (Find in Files). That said it'd be nice to have this in Ctrl+F and not just Ctrl+R, imo. (I understand the reasoning for why not, but still consider it a worse UX).
Comment 1 Lassi Väätämöinen 2024-06-28 16:06:27 UTC
(In reply to Quinten Kock from comment #0)
> SUMMARY
> In the Kate search panel, there are currently options to "Match case" and
> "Enable regular expressions".
> Additionally, in the Kate Ctrl-F bar, there's a button for Match case.
>
> It would be nice to add a way to easily filter matches by whole word 
>
> GUI button is easier to use for most users.
> 
> ADDITIONAL INFORMATION
> There was a request for this in Ctrl-F before: bug 290010. However that does
> not cover Ctrl+Shift+F (Find in Files). That said it'd be nice to have this
> in Ctrl+F and not just Ctrl+R, imo. (I understand the reasoning for why not,
> but still consider it a worse UX).

Really cofusing wishlist, but I read this as follows, so the requests here are:
1.  "Match whole word" -button to be added to Ctrl+F
2. "Match whole word" -button to be added to Ctrl+Shift+F

For request 1:  https://bugs.kde.org/show_bug.cgi?id=290010#c3 states:
> This is by design, and it works pretty well. We cannot add all sorts of options to the simple find, because then
> 1. it is not simple anymore, and
> 2. there is not enough space. Hence, this won't change ;)

-> "Match whole word" ewrks as specified, through the Power Search (Ctrl+R)

For request 2, add "match whole word" button to Find In Files function:
Seems to be indeed missing. Is there a design restriction here?
Comment 2 Kåre Särs 2024-06-30 07:48:57 UTC
The only reason the "match whole word" is missing from the Find in Files is UI clutter.

We already have 12 buttons in the common for all search places. Is the "match whole word" worth the extra button, space or added clicks for the rest of the workflows? 
As it is right now, you can see with just a glance if you have "match case" and/or "regular expression". Adding a "match whole word" would mean that the tool-button for "regular expression" would have to be converted into a combo-box that takes three or four times more space...

That said, if there are ideas on how to improve the UI, I'm willing to listen ;)
- I don't want the required space to increase
- I want the important settings to always be visible (like "match case" and "use regular expressions")


Hmm... We have the regular-expression menu button in the search combo-box.... that mechanism could maybe be used for also selecting the search mode, but is that discoverable enough?
Comment 3 Bug Janitor Service 2024-07-15 03:46:33 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 4 Bug Janitor Service 2024-07-30 03:46:12 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!