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 671506 - Replace the shortcut Ctrl+N with Ctrl+T and create a Ctrl+Tab keyboard shortcut in Gedit
Replace the shortcut Ctrl+N with Ctrl+T and create a Ctrl+Tab keyboard shortc...
Status: RESOLVED DUPLICATE of bug 588702
Product: gedit
Classification: Applications
Component: general
3.3.x
Other Linux
: Normal enhancement
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-06 22:56 UTC by Nick
Modified: 2012-03-07 09:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nick 2012-03-06 22:56:29 UTC 
I love how Gedit makes use of some of the same keyboard shortcuts for dealing with tabs as the Firefox web-browser (e.g., Ctrl+W, and Alt+1-0). This
really contributes to ease-of-use.

Yet two important keyboard shortcuts are missing from Gedit: Ctrl+T and Ctrl+Tab.

Please replace the current Ctrl+N keyboard shortcut with Ctrl+T for creating new tabs in Gedit. Ctrl+N is customarily used for creating a new window (not a new tab). The keyboard shortcut Ctrl+T should be the one used for creating a new tab.

In addition, please create a Ctrl+Tab keyboard shortcut for advancing the input-focus through open tabs in gedit.

Creating these keyboard shortcuts for Gedit would increase Gnome's ease-of-use because these are the same keyboard shortcuts used by all major web-browsers, and hence what everyone is already familiar with.
Comment 1 André Klapper 2012-03-07 09:50:11 UTC 
Looks like a duplicate of bug 588702 to me.
Comment 2 Ignacio Casal Quinteiro (nacho) 2012-03-07 09:51:15 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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