Bug 9134 - MonoDevelop doesn't obey Mac OS User Key Bindings
Summary: MonoDevelop doesn't obey Mac OS User Key Bindings
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 3.1.x
Hardware: Macintosh Mac OS
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-12-26 20:14 UTC by Anonymous
Modified: 2017-07-21 17:16 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Home/End combos Dict file (610 bytes, text/plain)
2012-12-26 20:15 UTC, Anonymous

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 9134 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Anonymous 2012-12-26 20:14:15 UTC
It seems MonoDevelop seems to have its own key bindings for the core OS bindings that it Mimics but doesn't actually check to see what the user has set them to be.  So when you change them in a user profile and reboot MonoDevelop doesn't change, and they are not exposed via the MonoDevelop -> Preferences -> Key Bindings to change.

Basically the Home and End key's have been change via Apple approved methods using the ~/Library/KeyBindings/DefaultKeyBinding.dict file. You can override just about everything at the OS level using this file.  Many people like to change Mac's Home and End to be more Windows like because they make more sense. I Have attached my sample dict file.  It only changes the Home/End combos using mac conventions like CMD instead of Ctrl. 

It would make sense if MD observed the OS level key bindings so if they are changed then they are still using what the user expects, however if it would exposed them via its internal Key Binding however that would be a lot to expose as there is more than just the Home/End combos.

My Version of MD:

MonoDevelop 3.1.1
Installation UUID: 5051fd40-f4ac-49d3-b9cd-8d23ec98017d
	Mono 3.0.2 (master/9e7f206)
	GTK 2.24.11
	GTK# (
	Package version: 300020000
Apple Developer Tools:
	 Xcode 4.5.2 (1847)
	 Build 4G2008a
Xamarin.Mac: Not Installed
Mono for Android: Not Installed

Monotouch: 6.0.8
Build information:
	Release ID: 30101000
	Git revision: 5d928ec4f9d5864b4db04a1301b8a8649b43fb9d
	Build date: 2012-12-14 19:11:30+0000
	Xamarin addins: 80f2dcc8fe4ed316b3e77dde496fc33d90305047
Operating System:
	Mac OS X 10.8.2
	Darwin GnomeBook.local 12.2.0 Darwin Kernel Version 12.2.0
	    Sat Aug 25 00:48:52 PDT 2012
	    root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64
Comment 1 Anonymous 2012-12-26 20:15:08 UTC
Created attachment 3132 [details]
Home/End combos Dict file
Comment 2 Mikayla Hutchinson [MSFT] 2012-12-28 08:07:59 UTC
Fully supporting this for all commands would be a difficult problem for the UI of the MD keybindings editor, as it would be difficult to make it clear which bindings were OS level, which were MD level, and how the MD bindings (or unbindings) overrode the OS ones.

It might make more sense implement it for just some of the "built-in" behaviours of the text entry widgets, instead of integrating with the MD command system. Making this work across everything (not just the main text editor) would require GTK changes.
Comment 3 Anonymous 2012-12-28 20:21:02 UTC
OR you can just see what the user has set in their ~/Library/KeyBindings/DefaultKeyBinding.dict. If it doesn't exist then change nothing, if it does parse it and make sure you map to those. You wouldn't have to expose anything in the UI for this. The user said "I WANT THESE KEYBINDINGS AT THE OS LEVEL" and I would think they should be respected.

Also I think this is really something GTK should be handling, as all GTK apps would have this issue and pushing the fix down to GTK helps more than just MonoDevelop. However I really use so few GTK apps other than MD, so as long as MD works as the OS key bindings are set by the user.