https://bugs.kde.org/show_bug.cgi?id=465814
--- Comment #4 from Grósz Dániel <groszdaniel...@gmail.com> --- (In reply to Waqar Ahmed from comment #3) > We have decided to keep the behaviour for now. See linked MR: > https://invent.kde.org/utilities/kate/-/merge_requests/1113 Regarding the comments there (not sure if I should respond here or there): I didn't propose changing the Documents sidebar at all (I like its current behavior of opening any file you click in the focused split), only the Ctrl+Tab behavior. VSCode has tabs, and Ctrl+Tab works like I proposed (separate orders, and only showing the tabs in the current split view). Qt Creator doesn't have a concept of which files are open in a given split view, but the Ctrl+Tab order is per-split there too. Visiting a file in one split doesn't bring it forward in the Ctrl+Tab order of another split. KDevelop, OTOH, works like Kate currently; there, the equivalent of my proposal is a confirmed request since 2013: Bug 323218. Eclipse seems to behave rather differently, such that views can be arranged in many ways, and it seems to have a single Ctrl+Tab order, but it will switch to a different (split) view if necessary, rather than open a file in the current view. In LyX (not a plain text editor, but also has tabs and splits), Ctrl+Tab switches in the order tabs are on the tab bar, per-split, rather than in the order they have been last used. (Kate has different shortcuts for this by default.) However, I was wrong that the current Kate Ctrl+Tab behavior started last year: I built 21.12 and it also worked like this. I guess I thought it started with 22.04 because the most noticeable effect—Ctrl+Tab reopening a tab I just closed with Ctrl+W—didn't happen until then because closing a tab closed it everywhere. -- You are receiving this mail because: You are watching all bug changes.
