After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 595465 - make [ctr]+g take focus of goto page no. textbox
make [ctr]+g take focus of goto page no. textbox
Status: RESOLVED DUPLICATE of bug 474079
Product: evince
Classification: Core
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-09-17 14:41 UTC by Praveen Thirukonda
Modified: 2009-11-30 14:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Praveen Thirukonda 2009-09-17 14:41:05 UTC 
in evince there is no entry in the menu bar to go to a specific page no. hence using the keyboard i cannot just jump to any page no. of my choice.
Comment 1 Carlos Garcia Campos 2009-09-17 15:02:02 UTC 
ctrl + l should work
Comment 2 Praveen Thirukonda 2009-11-14 09:54:57 UTC 
(In reply to comment #1)
> ctrl + l should work

why was that combination decided upon?
ctrl +g seems more intuitive for a Go to page function
maybe we can have both?
Comment 3 Emmanuel Fleury 2009-11-29 17:54:44 UTC 
Two short-cuts for one feature seems a bit over-killing to me. Don't you think ?
Comment 4 Praveen Thirukonda 2009-11-30 13:53:53 UTC 
Well, ctr +g seems more intuitive so setting it would be nice. especially for people coming from windows where in most apps ctr+g is for the go to operation. iirc some GNOME apps also follow this though i dont remember which right now.

as for having 2 shortcuts, in some circumstances it seems justified (like here) to keep everyone happy.

also having 2 shortcuts doesnt really do any harm. its not like it adds bloat or anything.
Comment 5 Emmanuel Fleury 2009-11-30 14:20:05 UTC 
Ok, but switching this issue as 'enhancement' as it is not a bug.
Comment 6 Emmanuel Fleury 2009-11-30 14:22:27 UTC 
In fact, it appears that this issue was already submitted. :)

*** This bug has been marked as a duplicate of bug 474079 ***