Synergy

Issue Tracker (powered by SPIT)

Bug #2370 - internal keyboard mapping on Mac OS X ignored

Status:
WontFix
Priority:
Normal
Assignee:
None
Category:
None
Target:
None
Found:
None
Created by:
Created on:
23 Aug 2005 17:20
Updated by:
None
Updated on:
9 Aug 2010 22:31
Platform:
None
Google ID:
sf-126
Redmine ID:
2402

SourceForge user: urkle

I have my Mac OSX installation configured to map the
caps-lock key to the apple key as my keyboard does not
have an apple key or a windows key and I rarely use the
caps-lock anyway. However when I use synergy and the
mac os x box is a client, the caps-lock is sent AS a
caps-lock and not mapped to the Apple key.

Also I saw now way of mapping the caps lock to the
apple with the synergy.conf.


#1

27 Aug 2005 21:07: Issue Importer wrote a comment.

SourceForge user: crs23

Logged In: YES
user_id=21565

This is not a bug. Caps-lock is sent as caps-lock because it's caps-lock
on the server. If you want it to act like the command key then map it to alt
on the server. If you map it to a windows key it'll be the option key on the
mac. If you do that mapping (or already have) and it's still sent as caps-
lock then that is a bug and i'll reopen.