Bug 418726 - Caret does not match the beginning of a line
Summary: Caret does not match the beginning of a line
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: search (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-11 00:00 UTC by Henry Pfeil
Modified: 2020-12-13 04:34 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henry Pfeil 2020-03-11 00:00:52 UTC
SUMMARY
When you enter '^' in the find/replace in the find ui QLineEdit widget, no matches are found. You should be able to insert a string at the beginning of a line. It works if you include the first character of the line, you can insert the replace string at the beginning of the line with the fist char appended to the replace, but with different first chars, that is not an option.

STEPS TO REPRODUCE
1. Type a caret into the find linedit widget
2. Type a string in the replace linedit widget
3. 

OBSERVED RESULT
No matches found.

EXPECTED RESULT
There should be a match at the beginning of each line in the file so you don't have to resort to `sed 's/^/somestring/'`.

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

ADDITIONAL INFORMATION
Suggest replace QRegEx with QRegularExpression, as the Qt docs recommend.
Comment 1 Justin Zobel 2020-11-13 05:14:44 UTC
Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 2 Bug Janitor Service 2020-11-28 04:33:51 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 3 Bug Janitor Service 2020-12-13 04:34:02 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!