SUMMARY When I temporarily change the font size by zooming with Ctrl++ or Ctrl+-, I have to do it for every document instead of just once. I mainly use the zoom feature when moving Kate from my 15.6 inch FHD laptop screen to my 27 inch 4K screen (1x scaling for both). SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210311 KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.4-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD RENOIR
In principle I understand that this would make sense. On the other side at the moment all settings one does on one view are local (and e.g. unlike global settings in the config dialog non-persistent).
(In reply to Christoph Cullmann from comment #1) > In principle I understand that this would make sense. > > On the other side at the moment all settings one does on one view are local > (and e.g. unlike global settings in the config dialog non-persistent). If Kate was more like a web browser or word processor where multiple font sizes and layouts with different proportions can be used in different open documents, then I think the current behavior would make more sense. As it is, I think it gets in the way.
(In reply to Noah Davis from comment #2) > (In reply to Christoph Cullmann from comment #1) > > In principle I understand that this would make sense. > > > > On the other side at the moment all settings one does on one view are local > > (and e.g. unlike global settings in the config dialog non-persistent). > > If Kate was more like a web browser or word processor where multiple font > sizes and layouts with different proportions can be used in different open > documents, then I think the current behavior would make more sense. As it > is, I think it gets in the way. The question is: should we then e.g. make all View-> stuff global? I guess it would make sense. I rarely want e.g. line numbers for one view but not for others.
I have no real idea if we should really alter it. ATM all stuff is there view/document specific. Which IMHO isn't that strange, given you want to set e.g. the highlighting mode for sure per document. On the other side, perhaps some things might be better global, but then it again is rather inconsistent, too. e.g. font size will be global, highlighting local, what with other options?
I think per document zooming is useful, I have seen a lot of users do it for 1 document temporarily for e.g if they are showing something to someone on the screen. But it also makes sense if it is available as a global option. Maybe we should ask about it in reddit or something and try to see what users expect. It would also make sense to check what other editors do.
At least VS Code just zooms the whole window (including the full UI), which IMHO is very strange, but I guess a side effect of that it is just a web browser :)
Vscode has a different zoom action for zooming only the editor. You can find it via their command bar. Just checked it, it seems to zoom in all open tabs and not just one.
(In reply to Noah Davis from comment #2) > (In reply to Christoph Cullmann from comment #1) > > In principle I understand that this would make sense. > > > > On the other side at the moment all settings one does on one view are local > > (and e.g. unlike global settings in the config dialog non-persistent). > > If Kate was more like a web browser or word processor where multiple font > sizes and layouts with different proportions can be used in different open > documents, then I think the current behavior would make more sense. As it > is, I think it gets in the way. New user opinion: 100% agree. With a text editor I'd expect it to zoom all documents if they are in same application window. I often have so many documents open that current behavior make functionality not really useful. However, different application windows having own zoom level is great to have and makes more sense since they can be in different monitors with different DPI.