When you press the cursor keys, modified cursor keys (with [Shift], [Ctrl], and so on) or [Home] and [End] keys on a Windows PC, the on-screen cursor reacts in a consistent way when it’s in a block of text, no matter what application you’re using. Its behaviour is controlled at operating system level rather than individual application level, and this consistent behaviour is a sign of good user interface design.
Now I’m the last person to suggest that Windows is any kind of benchmark for good interface design – in fact one of the reasons I recently switched to a Mac was the UI horror of Windows Vista and Windows 7. And, of course, the Mac has a wonderfully consistent user interface that’s far more logical and intuitive than anything Microsoft has so far managed. Apart from its stupid cursor control.
For example, the [Home] and [End] keys on a Windows PC keyboard always – always – move the cursor to the start or end of a line. In Mac OS X, they do not (true, they are labelled with ↖ and ↘ and while this could mean jump to the start or the end of a document, they don’t do that. Well, not often).
In NeoOffice Writer on the Mac, however, those same keys move the cursor along by a word at a time. In Firefox, on the other hand, they act as Page Back/Forward buttons, even when you’re editing text in a text box – which, as you can imagine, can be quite frustrating when you’re trying to type a sizeable block of text.
Back in NeoOffice Writer, [Ctrl ]+ [↖] and [↘] keys move the cursor to the end of a line, but in Firefox, those modified keystrokes act as Page Up and Page Down – just like the separate [Page Up] and [Page Down] keys, in fact. Or the [⇞] and [⇟] keys, if you want to be pedantic.
I could go on, but I won’t, because this level inconsistency in an operating system that prides itself on user-friendliness is utterly ridiculous. And I’m not the only one to think this – the first thing anyone looking for a similar solution is likely to find is a System Preferences Pane add-in called DoubleCommand. This lets you modify the keyboard in a number of ways, including enabling ‘PC style Home and End keys’. Sounds ideal, but it doesn’t work.
Many Mac OS applications (it seems) can be tweaked to alter the way in which they react to certain keystrokes and NeoOffice is indeed one of them. Its Tools > Customize > Keyboard option doesn’t work either.
Is there a way to modify Firefox’s keyboard shortcuts? I have no idea – I’ve give up trying to find out. I’ve categorised this silly inconsistent keystroke shortcoming as one of the Mac’s foible’s and it’s either one that Apple probably denies has ever been a problem, or one that Mac users are so used to that they wouldn’t have it any other (albeit better) way.
So, the title of this post is a fib – I don’t know how to fix the Mac keyboard to work properly. But I would like to know if it’s possible. So, if you know how, please tell me. Please…

[...] complained at length about keyboard shortcut inconsistencies in Mac OS X the other day — an OS that’s supposedly ultra-consistent — but it appears that the Apple [...]
thank you for your post
and doubleCommand does work BTW
Just found this link which discusses this very frustration! There's a solution for it here:
http://lifehacker.com/software/keyboard/mac-swi...
Yes, DoubleCommand does work! It's the kernel driver so you must reboot to make it active.
Hm, I must beg to differ… Try opening a text document in NeoOffice — those two keys still don't move the cursor to the start/end of a line. Now this could well be a NeoOffice issue, but the fact remains that DoubleCommand isn't a global fix. ;)
IMO there is no global fix. Any application can change the keyboard mapping and obvoiusly many of them are doing this. DoubleCommand works for me in many Cocoa apps like text editor, mail, Safari (when I am editing this comment for example). Anyway – you are right – the consistency of Mac keyboard shortcuts is far behind the Windows. Terrible example is the Address Book item editing. Command + Right moves the cursor to the end of line. Command + Left does nothing, but … after releasing the Command button pressing the Left selects the item and the next Left moves the cursor to the start of line. iCal event editing works as expected. I really do not understand, why the Mac programmers are changing such basic behaviour like 'move cursor to the start/end of the line'.
This one seems to work:
http://lifehacker.com/software/keyboard/mac-swi...
Have fun!
http://www.starryhope.com/tech/apple/2006/keyfi...
Works like a charm!
I haven't tried it yet, but this does look promising!
http://lifehacker.com/225873/mac-switchers-tip-...
Good luck!
Solution:
http://lifehacker.com/225873/mac-switchers-tip-...