SUMMARY It would be nice if Kate/Kwrite provided some indication of how many files are open in its tabs, so this info would be reflected on the respective entry in the Task Bar panel. The easiest way to do it, I think, is to provide this info on the Kwrite/Kate title bar as the Task Bar/Manager uses the app's title bar info to show the app's entry, right? JUSTIFICATION Kwrite now allows to open several files in tabs instead of opening several Kwrite windows. Suppose, there are 3 file open in tabs in Kwrite, say, f1.txt, f2.txt and f3.txt. When looking at the Task Bar panel the user sees something like "f1.txt -- Kwrite" for the Kwrite app, there is no indication that other files are open in Kwrite. It would be useful to me if there was some kind of indicator reminding that there are other files open in the Kwrite. For example, instead of showing "f1.txt -- Kwrite" in the Task bar, something like "3t -- f1.txt -- Kwrite" could be shown, where 3t is an indication that 3 tabs are currently open in Kwrite. SOFTWARE/OS VERSIONS Operating System: Debian 12 Bookworm GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-6-amd64 (64-bit) Graphics Platform: X11
Hmm, not sure about that. I doubt a average user would understand the XXXt stuff or any other number there. Beside I fail to see that other editors like Code do that.
(In reply to Christoph Cullmann from comment #1) > Hmm, not sure about that. > I doubt a average user would understand the XXXt stuff or any other number Why wouldn't the average user understand it if it's documented? I think an indicator reminding the user that there are other files open in Kwrite/Kate besides the file that's shown on the Task Bar would be very useful. The "3t" example I used above is just one possibility but, of course, it could be done in many ways, for example: "+ f1.txt", "+3 f1.txt", "+3t f1.txt", etc. Also, this feature could be may optional, that is, there would be a config setting to turn it off, if desired. > Beside I fail to see that other editors like Code do that. So what? Maybe they'll adopt it after it's implemented in Kwrite/Kate.