From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <dd6fe68a0907012026r73b8985bgb0376147df374b9a@mail.gmail.com>
References: <d557e03ffc14ff82ef4d18fd612fd5ec@terzarima.net>
	<F5173FA4-EB78-4150-84C5-4CF7BDE4719B@gmail.com>
	<20090701192454.GA31691@jg.domain_not_set.invalid>
	<dd6fe68a0907011249u24705685qa0a8018b89322ed1@mail.gmail.com>
	<3e1162e60907011358w7662ff53je2304e7266c2fa8e@mail.gmail.com>
	<7d3530220907011413j3ad2ef9bn336370142924c33c@mail.gmail.com>
	<5d375e920907012004g7c25a8c2j493c5e848367f4f0@mail.gmail.com>
	<dd6fe68a0907012026r73b8985bgb0376147df374b9a@mail.gmail.com>
Date: Thu,  2 Jul 2009 05:38:15 +0200
Message-ID: <5d375e920907012038y16f861aan7e1ac960af0776e5@mail.gmail.com>
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Guide to using Acme effectively?
Topicbox-Message-UUID: 12eaecba-ead5-11e9-9d60-3106f5b1d025

On Thu, Jul 2, 2009 at 5:26 AM, Russ Cox<rsc@swtch.com> wrote:
>> Anyway, hope people finds it useful, and please send me any extra info
>> on how to implement/configure/restore the standard Unix behavior in
>> any other environments and apps.
>
> On a Mac:
>
> mkdir -p $HOME/Library/KeyBindings
> cat >$HOME/Library/KeyBindings <<EOF
> {
> =C2=A0"^u" =3D "deleteToBeginningOfLine:";
> =C2=A0"^w" =3D "deleteWordBackward:";
> }
> EOF
>
> will make ^U and ^W work across all applications.

Awesome! I added it to http://unix-kb.cat-v.org/OSX

Thanks!

>> P.S.: I even recently wrote a Google Chrome extension to implement the
>> Unix text editing keyboard shortcuts in web pages, it works fairly
>> well so far: http://repo.cat-v.org/burning_chrome/hosaka/ next task is
>> implementing acme-like mouse chording ;)
>
> Neat. =C2=A0If you could make the tab key actually generate
> a tab character, that would be fantastic.

Ah, that is a good one, I think it should be possible, I will try to
get it for the next version (need to update for the new extension
packaging format anyway).

I do override the extremely annoying mapping of backspace to the back
button when a text field is not focused, which is also extremely
frustrating when you hit it by mistake and your current page (often
with all text) is lost.

Oh, and note that unfortunately due to current limitations in the
Chrome extensions API, this changes only apply to text fields in the
page, not to the url bar :(

uriel

>
> Russ
>
>