#Change command to control mac for mac osx

The patch osx-swapkeys+numlock.patch fixes both this bug and #453 for me. Swap control and meta keys and also deal with numlock as per #453 Wed, 06:21:01 GMT - Antoine Martin: attachment set Wed, 06:15:30 GMT - Antoine Martin: attachment set Included ctrl, ctrl-c, ctrl-v, command, cmd-c, cmd-v. osx 10.9, using Xpra.app/Contents/Helpers/Keyboard_Tool. Osx local key mappings of ctrl and commandДЄttached *raw* keyboard data as requested. Set to osx-local-ctrl-v-cmd-key-mappings.txt Looks like some modifier is mis-mapped and causing NumLock to fire. Please post *raw* keyboard data, without xpra interfering. Updating bug title: the client does exactly what is expected (bar NumLock issues) but we need to swap the two keys around to make *nix applications do what mac users expect in terms of key mapping. keywords keyboard added command v ctrl removed.

#Change command to control mac for mac osx

Sat, 08:55:51 GMT - Antoine Martin: status, description, summary, owner, keywords changed milestone setД¬hanged from osx client treats ctrl key as osx would generally treat the command key to swap command and control key for mac osx clientsД¬hanged from Antoine Martin to Antoine Martin Set to xpra_keyboard_output_control-v-command I'm attaching a (hopefully) illustrative file of the behavior with the gtk_view_keyboard tool. (Oddly, it seems that the xpra interprets the command key as a non-sticky NumLock key.) Ideally, the ctrl functionality can be mapped to command for the osx client. but the osx client xpra sessions dont' recognize command-c - rather recognizing ctrl-c as a windows client would expect. When using osx one expects command-c to copy, for instance.