Re: [gtk-osx-users] cut/copy/paste accelerators on Mac

[John Ralls <jralls ceridwen us>]

> On Dec 26, 2014, at 2:28 PM, Brecht Machiels <brecht__gmane mos6581 org> wrote:
>
> Ignore this one. Wrong mailing list of course.
>
> On 2014-12-26 21:40:52 +0000, Brecht Machiels said:
>
> > Hello,
> > I'm running into a problem with PyGTK on OS X. Please find the
> > description below (originally posted to the GTK+-2 OSX Users mailing
> > list).
> > On 2014-12-26 19:13:32 +0000, John Ralls said:
> > > > On Dec 26, 2014, at 9:33 AM, Brecht Machiels wrote:
> > > > With gtkosx-application installed, I have managed to move Zim menus to
> > > > the OS X menu bar and About/Preferences/Quit to the application menu
> > > > without much trouble, but there are some problems remaining.
> > > > 3) I changed all of Zim's keyboard accelerators to use <Primary>
> > > > instead of <ctrl>. This works as expected for all accelerators in the
> > > > main Zim text editor widget. However, in other widgets (such as a
> > > > search box), the Cmd-x/c/v accelerators do not work. Ctrl-x/c/v do,
> > > > however.
> > > > I did come across the "modifyng Gtk-2 keybindings" thread on this
> > > > mailing list, where it was recommended to set
> > > >    gtk-key-theme-name="Mac"
> > > > in ~/.gtkrc-2.0
> > > > While this doesn't work with the Homebrew GTK+, adding
> > > >    include
> > > > "/usr/local/Cellar/gtk+-quartz/2.24.11/share/themes/Mac/gtk-2.0-key/gtkrc"
> > > > should have the same effect, I think.
> > > > Now, the search box in Zim's main window will work with Cmd-x/c/v, but
> > > > text widgets in other windows (dialogs) don't, and they won't react to
> > > > Ctrl-x/c/v anymore either. Is there any way to make this work as
> > > > expected?
> > > Possibly not. PyGtk hasn't been maintained for some time and may not
> > > have kept up with the changes to the key handling code in Gtk+-2.24. It
> > > has nothing to do with gtk-mac-integration, which only handles menus.
> > What could explain the Cmd+x/c/v accelerators not working in dialogs?

Another thought occurred to me: You said that setting gtk-key-theme-name=“Mac” in ~/.gtkrc-2.0 doesn’t work 
in the (rather ancient) Gtk+ built by Homebrew. Maybe there’s a message there, that Homebrew tampers with the 
gtk source in a misguided effort to provide the functionality in a different way.

Regards,
John Ralls