[haiku-development] Re: Keymaps and Command key
- From: "Ari Haviv" <arielbhaviv@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 20 Aug 2008 00:05:18 -0400
On Tue, Aug 19, 2008 at 9:35 PM, Jorge Mare <kokitomare@xxxxxxxxx> wrote:
> On Tue, Aug 19, 2008 at 6:19 PM, Ari Haviv <arielbhaviv@xxxxxxxxx> wrote:
>> Haiku should be about sane defaults. Control C for copy, etc is
>> default for Windows as well as gnome and kde on linux, even though it
>> does something else in terminal.
>
> And that's exactly the kind of inconsistency that Haiku does not need to
> mimic.
>
> Jorge
>
>
Yes. Gnome tries to get around it with a shift control c combination
in terminal. Not only is the inconsistency still there but the
addition of the shift makes it harder to type. Of course, the
inconsistency is tolerated because "we have to make it easy to attract
the windows users"
This was a big issue for Be. JLG felt it was so important to have the
control c option that he made it priority number one.
see http://www.osnews.com/story/7265
Times have changed. Haiku is first introduced to the linux community,
not mac or windows. And the command line, instead of thrown under the
rug as some obsolete anachronism, is now embraced by Mac and Microsoft
(powershell).
Another point: BeOS was intended to coexist with Windows, not replace
it. "Use BeOS for media and windows for everything else." If you have
to dual boot most of the time (or use wine) then alt c here and
control c there would be a major inconsistency.
Other related posts:
