SUMMARY Cannot see current cursor coordinates when search bar is open. The search bar appears on top of status bar, it becomes totally hidden. STEPS TO REPRODUCE 1. Press Ctrl+F 2. 3. OBSERVED RESULT No current line number on screen. EXPECTED RESULT Need current line number somewhere on screen. SOFTWARE/OS VERSIONS Operating System: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.1.17-300.fc30.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15,4 ГиБ ADDITIONAL INFORMATION
If you only need the line number (and not the column number), try enabling Settings -> Configure kate -> Appearance -> Borders -> Show line numbers.
Alexander, we are aware of this and I'd argue this is by design. What is missing in your report is why do you need to know the line and column when you search for text? What is the use case?
I know I can enable the line numbers, but I prefer not to enable them because I'm too lazy to change the default settings. Even after I enable line numbers, it won't be perfect UX because I'm used to looking at the status bar for the current line number, not at the column to the left of the editor. Use case: 1. I search for something in the file, then 2. need to check the line number of either pattern occurrence or some other text. 3. Don't want to spend my time on another "Ctrl-F + Esc" before seeing the current line number. (The Ctrl+F is necessary because I could unfocus by mouse click inside the editor - my habit, could be OCD.)
They are actually enabled by default now. :)
(In reply to Dominik Haumann from comment #2) > Alexander, we are aware of this and I'd argue this is by design. What is > missing in your report is why do you need to know the line and column when > you search for text? What is the use case? For me, trying to work on some ktexteditor/kate code that has to do with KTexteditor::Range/Cursor classes, where, when I am testing after compiling, I have to keep closing the searchbar (either the incremental or the power one) to see the column number... (In reply to Alexander Potashev from comment #3) [...] > 3. Don't want to spend my time on another "Ctrl-F + Esc" before seeing the > current line number. (The Ctrl+F is necessary because I could unfocus by > mouse click inside the editor - my habit, could be OCD.) FWIW, pressing Esc will close the search bar even if it doesn't have focus.
Ok, let's assume you have a point. How should the workflow be improved to resolve this?
(In reply to Dominik Haumann from comment #6) > Ok, let's assume you have a point. How should the workflow be improved to > resolve this? Well, we could revive the previous behaviour: the search bar appears in a separate row above the statusbar, just like Okular and Konqueror do.
Then we again waste space and for the one-liner variants your view jumps around on showing find/goto/.... The current behavior is there for some reason and I not really see the concrete need to change it. Line numbers are now "on" per default.
I think this discussion needs feedback from UX experts.
Yeah, I think it would make sense to show and hide a separate search bar rather then replacing the contents of the status bar with the search field. Pretty much all other apps I use show and hide a separate search bar--including our own!
Alone that showing search or goto doesn't resize my views is enough of a reason I will not alter this, sorry. We tuned that years ago to behave that well (the only issue is replace, that needs a two line widget).
If somebody provides a patch to make it an configurable feature to have the status bar always visible and the other bottom widgets located "above" it (default off), I would be willing to accept that. If nobody steps up, we can expire this request some when in the future.
Fixed in 5.92