Bug 429818 - Autoscroll file a bit to show line context when searching
Summary: Autoscroll file a bit to show line context when searching
Status: RESOLVED INTENTIONAL
Alias: None
Product: kate
Classification: Applications
Component: search (show other bugs)
Version: 22.12.3
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-29 18:05 UTC by Andrew Shark
Modified: 2024-03-15 20:49 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
A video showing that you cannot see a context of first match without manually scrolling up (1.17 MB, video/mp4)
2020-11-29 18:05 UTC, Andrew Shark
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Shark 2020-11-29 18:05:46 UTC
Created attachment 133732 [details]
A video showing that you cannot see a context of first match without manually scrolling up

When searching in kate, when you hop next match with f3, you often cannot see a context of the line in which match was occured. It would be nice to automatically scroll a bit (I think 5-10 lines would be ok), so user can see the context.
See attached video showing a problem.

Operating System: Arch Linux
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Comment 1 Andrew Shark 2020-11-30 11:44:31 UTC
I have noticed that jumping between bookmarks (atl+pgup and alt+pgdn) just places the bookmarked line in the center of text area. Maybe it is better to make the same for search matches with F3/shift+F3? So the context will always be visible when searching forward or backward.
Comment 2 Justin Zobel 2020-12-02 01:08:51 UTC
I've moved this to wishlist as it's not a bug but a feature request. I agree it would be nice to be able to see some context around the search term.
Comment 3 Christoph Cullmann 2023-04-16 16:41:49 UTC
Dear user, this wish list item is now closed, as it wasn't touched in the last two years and no contributor stepped up to implement it.

The Kate/KTextEditor team is small and we can just try to keep up with fixing bugs.

Therefore wishes that show no activity for a years or more will be closed from now on to keep at least a bit overview about 'current' wishs of the users.
If you want your feature to be implemented, please step up to provide some patch for it.

If you think it is really needed, you can reopen your request, but keep in mind,
if no new good arguments are made and no people get attracted to help out to implement it,
it will expire in a year again.

We have a nice website https://kate-editor.org that provides all the information needed to contribute, please make use of it.

e.g. see the information at https://kate-editor.org/join-us/ for details

Greetings
Christoph Cullmann
Comment 4 Andrew Shark 2023-04-17 20:10:33 UTC
Still valid feature request for Kate 22.12.3
Comment 5 Christoph Cullmann 2024-03-15 20:13:07 UTC
(In reply to Andrew Shark from comment #4)
> Still valid feature request for Kate 22.12.3

It is, but it will not happen if nobody provides a patch.
We will not keep feature requests open for ever, if x years nobody shows up to do it, we close them.
Comment 6 Andrew Shark 2024-03-15 20:39:24 UTC
> We will not keep feature requests open for ever, if x years nobody shows up to do it, we close them.

Wow. Super strange policy. Did not see such thing for any other projects. Some bugs are opened for decades!
Comment 7 Christoph Cullmann 2024-03-15 20:49:35 UTC
(In reply to Andrew Shark from comment #6)
> > We will not keep feature requests open for ever, if x years nobody shows up to do it, we close them.
> 
> Wow. Super strange policy. Did not see such thing for any other projects.
> Some bugs are opened for decades!

We did that in the past, it makes no sense to keep xxx feature requests open that are dormant.
Even with that regular cleaning we have a lot that will never be done.
If it is a bug and no missing feature it stays open, we have unfortunately bugs that are very old and yet not fixed.