Hello geany devs,
Before I describe this feature request, I am finally using geany AND also learning C++ (slowly ...). C++ is a lot more annoying than ruby but I guess the really interesting things are all in C/C++, so I knew I had to learn C and/or C++ eventually. But I digress.
To the topic:
That is, the content of that tab. So I can increase the font via pressing strg
on my german layout keyboard (I guess this is ... control key? Very bottom
left), then hit the mouse scrollwheel; upwards scrolling makes the font size
larger. Downwards scrolling decreases font size.
This is GOOD and CONVENIENT. But I have one problem:
My proposal is thus to:
This should be trivial in that we could send the same command/event
to all tabs, I think. (I know gtk only via the ruby-gtk bindings, but I
remember that the gtk notebook tab would often keep all tabs as
an array and one can address them and the buffer content).
So I think in theory, this feature should be trivial.
What may not be trivial is that perhaps some users may like the
existing behaviour, I have no idea. I don't mind to retain the current
status quo by the way, it is fine - but I would like to at the least
have an ADDITIONAL way to specify so that I can change all
tabs simultaneously.
I am not sure how to enable this best, but I will make two suggestions
and I am sure IF it is a worthwhile change, the geany devs will
think of an appropriate way (or another way; I am just trying
to give ideas):
a) the simple one is to add a checkbox to options/preferences, something
such as "synchronize changes to the font size" checkbox [yes/no] boolean
flag, and a tooltip that says something like "Enabling this checkbox will
apply font size changes to all tabs, not only the currently active tab." -
or something like that.
b) another option may be to add another keybinding. For example, strg
of course (a) and (b) can also be combined so both could be added. I
only wanted to provide a few ideas here. :)
Thanks for reading, feel free to close this issue at any moment in
time!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.