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 653783 - Does not support standard keybindings on OSX
Does not support standard keybindings on OSX
Status: RESOLVED DUPLICATE of bug 560738
Product: tomboy
Classification: Applications
Component: General
1.7.x
Other Mac OS
: High normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-30 22:36 UTC by papashou
Modified: 2011-06-30 22:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description papashou 2011-06-30 22:36:29 UTC 
OSX uses a set of keybindings that are common across applications.  Also, formatting options and other commands are not bound to the Command key (they are bound to the Control key which is not standard to the OS).  Make it possible to use the Command key  with these.  This will help improve OS integration. 

Examples below but not limited to:

Command+Q = quit
Command+B = bold
Command+U = underline
Command+I = italics
Command+H = highlight
Command+N = new (menu shows the Command key but it works with Control not Command).
Comment 1 Sandy Armstrong 2011-06-30 22:55:21 UTC 
Odd, I thought for sure we already had a bug for this, but I can't seem to find it.  Confirming, lowering severity, bumping priority.

Our goal was to make keybindings completely configurable, and simply ship different schemas on each platform.  Somebody was working on that but never finished it or provided a usable patch.

This commit is from a branch where I was playing with another approach, but I still prefer the idea of making all of our keybindings configurable:

http://git.gnome.org/browse/tomboy/commit/?h=mac-keybindings&id=fc2f34ca940335cb99a95c8d8ce06005be7e2a2a
Comment 2 Sandy Armstrong 2011-06-30 22:56:34 UTC 
Woo, found the dupe.

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