mactel-support team mailing list archive

[Peter Marks <peter@xxxxxxxxxxxxxx>]

Frankly, I am stunned that this ridiculous behaviour has made it into
the Hardy release. The suggestion that this is the behaviour that most
users would want or expect is quite preposterous.

If I plug a standard keyboard into a machine running OS X it behaves the
same as if I plug in an Apple keyboard. the same should be true on
linux. In OS X, the function keys are not used all that frequently, in
linux they are.

If you take the argument to it's conclusion, surely you should map
command-c to copy and command-v to paste. Surely this half based hack
satisfies no one.

Why does this need to be done in the kernel anyway? Could it not have
been accomplished in console tools and X? That way users could choose if
they wanted to customize their linux setup to be more like OS X.

I still not found any way to get my keyboard to behave as it did under
Gusty: function keys as function keys, num lock as num lock and the
backquote and backslash back where I expect them (UK layout).

-- 
Apple fn key behavior isn't consistent with what's expected
https://bugs.launchpad.net/bugs/201711
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.

Status in Mactel Support: New
Status in Source Package "linux" in Ubuntu: New
Status in Source Package "linux" in Suse Linux: Fix Released

Bug description:
Hi, this is a follow up to bug 162083.  With my newly functional FN key on my Aluminum BT keyboard, I realized that the default behavior on it doesn't make much sense with what users have come to expect on Linux systems.  The default behavior is that the "special keys", like f1-f2-f10-f11-etc all act "special" without pressing fn.  They then act normally when you hold FN.  This is the default behavior on Mac OSX, but on Linux the FN keys are more commonly used.  Eg, it's rather awkward to have to press ctrl-alt-fn-f1 to switch to a VT, or FN-F11 to set a terminal full screen.