9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Guide to using Acme effectively?
Date: Thu,  2 Jul 2009 05:38:15 +0200	[thread overview]
Message-ID: <5d375e920907012038y16f861aan7e1ac960af0776e5@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0907012026r73b8985bgb0376147df374b9a@mail.gmail.com>

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
> {
>  "^u" = "deleteToBeginningOfLine:";
>  "^w" = "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.  If 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
>
>



  parent reply	other threads:[~2009-07-02  3:38 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  8:56 Aaron W. Hsu
2009-07-01 14:31 ` erik quanstrom
2009-07-01 15:58 ` john
2009-07-01 16:46   ` Charles Forsyth
2009-07-01 18:53     ` J. R. Mauro
2009-07-01 19:24       ` blstuart
2009-07-01 19:38         ` erik quanstrom
2009-07-01 20:00           ` blstuart
2009-07-01 21:11             ` Ethan Grammatikidis
2009-07-01 21:18               ` John Floren
2009-07-01 21:31                 ` Felipe Bichued
2009-07-01 21:33                 ` Dan Cross
2009-07-01 21:41                 ` erik quanstrom
2009-07-01 21:56                   ` John Floren
2009-07-01 23:49                     ` J.R. Mauro
2009-07-01 22:08                 ` Ethan Grammatikidis
2009-07-01 22:23                   ` Connor Smith
2009-07-01 23:56                     ` john
2009-07-02  9:05                       ` Charles Forsyth
2009-07-02  9:29                     ` Aaron W. Hsu
2009-07-02  9:25                   ` Aaron W. Hsu
2009-07-01 23:47             ` J.R. Mauro
2009-07-02  9:25             ` Aaron W. Hsu
2009-07-01 20:26         ` Noah Evans
2009-07-01 20:42           ` erik quanstrom
2009-07-01 22:07         ` Charles Forsyth
2009-07-01 22:30           ` erik quanstrom
2009-07-02  9:21         ` Aaron W. Hsu
2009-07-01 19:24       ` Kris Maglione
2009-07-01 19:49         ` Russ Cox
2009-07-01 20:10           ` blstuart
2009-07-01 20:58           ` David Leimbach
2009-07-01 21:13             ` John Floren
2009-07-01 23:14               ` Lyndon Nerenberg
2009-07-02  3:04               ` Uriel
2009-07-02  3:26                 ` Russ Cox
2009-07-02  3:27                   ` Russ Cox
2009-07-02  3:38                   ` Uriel [this message]
2009-07-02 15:18                   ` Russ Cox
2009-07-02  5:04                 ` Ethan Grammatikidis
2009-07-02  5:39                   ` Rob Pike
2009-07-02  5:57                     ` John Floren
2009-07-02 11:15                     ` Uriel
2009-07-01 21:30             ` Ethan Grammatikidis
2009-07-02  1:47           ` Kris Maglione
2009-07-03 10:01           ` Balwinder S Dheeman
2009-07-03 12:34             ` sqweek
2009-07-03 17:41               ` Roman Shaposhnik
2009-07-04  1:52                 ` sqweek
2009-07-04 10:12                   ` hiro
2009-07-06  9:10                     ` Balwinder S Dheeman
2009-07-04 16:16                 ` Ethan Grammatikidis
2009-07-06 10:32                   ` mattmobile
2009-07-06 11:05                     ` Gregory Pavelcak
2009-07-06 17:59                       ` Ethan Grammatikidis
2009-07-06 18:57                         ` cinap_lenrek
2009-07-06 20:33                           ` Ethan Grammatikidis
2009-07-06 20:36                             ` John Floren
2009-07-06 21:08                               ` Ethan Grammatikidis
2009-07-06 20:40                             ` Jason Catena
2009-07-06 22:28                             ` J.R. Mauro
2009-07-02  9:17         ` Aaron W. Hsu
2009-07-04 17:49           ` ron minnich
2009-07-01 18:54   ` J. R. Mauro
2009-07-01 20:13 ` Jason Catena
2009-07-01 20:38   ` erik quanstrom
2009-07-01 21:17 ` yy
2009-07-01 22:20 ` roger peppe
     [not found]   ` <4A4C7CB9.4020804@proweb.co.uk>
2009-07-02  9:33     ` mattmobile
2009-07-02  9:19 ` Aaron W. Hsu
2009-07-02  9:29 ` Aaron W. Hsu
2009-07-02 22:48 ` J.R. Mauro
2009-07-03  9:02 ` Aaron W. Hsu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d375e920907012038y16f861aan7e1ac960af0776e5@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).