From: rob@plan9.research.att.com
To: <sam-fans@hawkwind.utcs.toronto.edu>
Subject: Re: binding commands to keys
Date: Fri, 18 Mar 1994 10:10:59 -0500 [thread overview]
Message-ID: <94Mar18.101122est.24182@hawkwind.utcs.toronto.edu> (raw)
i thought it was clear that part of the point of sam was to
separate functionality: input from the keyboard, control
from the mouse. with the exception of the scroll key,
which i did because of strong pressure and never use
myself, the division is firm and worked out well.
if you want to type funny characters at your editor
to make things happen, there's a wide variety of editors
out there. don't compromise the one editor that takes
a different stand.
-rob
next reply other threads:[~1994-03-18 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-18 15:10 rob [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-03-18 10:57 Steve_Kilbane
1994-03-18 10:19 Mark Robinson
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=94Mar18.101122est.24182@hawkwind.utcs.toronto.edu \
--to=rob@plan9.research.att.com \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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).