GNOME Bugzilla – Bug 607205
Help should explicitely say that zooming in is actually CTRL SHIFT +
Last modified: 2014-01-27 16:38:31 UTC
Problem: You need to zoom in and out of text. In order to do this, you need to use the View -> Zoom In menu item. When you are there, the keyboard shortcuts for it are confusing - the "CTRL++" command doesn't work (as per firefox's implementation, "Ctrl plus plus", "CTRL minus minus"). Finally, there's no mousewheel zoom either. Suggestions: * Reword the keyboard shortcuts for zoom in/out to "CTRL and +" "CTRL and -" to clarify it * Implement support for "CTRL(hold) + +" keystrokes (in), "CTRL(hold) - -" (out), CTRL 0 (reset) ala firefox. * Implement a mousewheel zoom
Ctrl-+ and Ctrl-- work here. Note that you may have to press shift as well, so the + is actually + and not =. This is bug 579681. I have no idea what "Implement support for "CTRL(hold) + +" keystrokes (in), "CTRL(hold) - -" (out), CTRL 0 (reset) ala firefox." even means.
Created attachment 163409 [details] [review] Add mouse wheel zoom in/out Ability to Ctrl-<mouse wheel> scroll in order to change terminal screen font size.
(In reply to comment #1) > Ctrl-+ and Ctrl-- work here. Note that you may have to press shift as well, so > the + is actually + and not =. This is bug 579681. It makes sense to the user who has understood the concept of keycaps having two symbols and to access the top symbol, one has to press Shift. I think we should be explicit about this in our help pages.
(In reply to comment #3) > (In reply to comment #1) > > Ctrl-+ and Ctrl-- work here. Note that you may have to press shift as well, so > > the + is actually + and not =. This is bug 579681. > > It makes sense to the user who has understood the concept of keycaps having two > symbols and to access the top symbol, one has to press Shift. I think we should > be explicit about this in our help pages. I'm changing the component to docs and the summary to be about that then.
(In reply to comment #3) > (In reply to comment #1) > > Ctrl-+ and Ctrl-- work here. Note that you may have to press shift as well, so > > the + is actually + and not =. This is bug 579681. > > It makes sense to the user who has understood the concept of keycaps having two > symbols and to access the top symbol, one has to press Shift. I think we should > be explicit about this in our help pages. We cannot predict which keyboard layout the user is using, so this cannot be fixed. I think it is safe to assume that a user using the terminal will know how to use a shift key, so it would be out of scope anyway.