9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Murdie <john@cs.york.ac.uk>
To: 9fans@cse.psu.edu
Cc: John Murdie <john@cs.york.ac.uk>
Subject: Re: [9fans] Emacs
Date: Wed, 12 Jun 2002 11:08:56 +0100	[thread overview]
Message-ID: <E17I53n-0001LI-00@minster.cs.york.ac.uk> (raw)
In-Reply-To: <404a8f744e2df45761206bdde489fbef@caldo.demon.co.uk>

On 12 Jun, forsyth@caldo.demon.co.uk wrote:
>>>>to research the reasoning and theory behind plan9 and acme? I realize it
>> >>is rather different style from traditional UNIX editing as well as the
>>>>Emacs style of editing, ...
>>>>
>>> i'd hope so after all this time. [i said]
>>>
>>read as "I understand it is easy to be preconditioned
>>by confident utilization of UNIX/Emacs style editing
>>over long periods of time, but, there is no reason to
>>dismiss a new environment without first learning how
>
> no, i meant today must be roughly 20 years later, surely,
> if not more.  i'd hope at least the style and ideally the substance
> might have changed a bit in these areas.   i realise that
> some older things turn out to be the best achievable,
> even in computing, and some newer things are
> worse than their predecessors.
> in this case, however, i can't help thinking that the elapsed time
> should provide some opportunity for interesting improvement.
>
> control-meta-shift-elbow!

Or, as someone here calls it: the ``Richard III interface''*, alleging
that one has to contort one's hands and body in order to issue certain
keyboard chorded commands.

* I read that Tudor propaganda portrayed Richard of York, one-time King
  of England, as ``Deformed, unfinished, sent before my time into this
  breathing world, scarce half made up.'' [Shakespeare, Richard III]
--

John A. Murdie
Department of Computer Science
University of York
England



  reply	other threads:[~2002-06-12 10:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12  9:07 forsyth
2002-06-12 10:08 ` John Murdie [this message]
2002-06-13  9:29 ` Don
  -- strict thread matches above, loose matches on Subject: below --
2002-06-12 17:56 anothy
2002-06-12  9:18 nigel
2002-06-12  7:49 Fco.J.Ballesteros
2002-06-11 10:08 forsyth
2002-06-12  8:54 ` Don
2002-06-10 10:31 nigel
2002-06-10 10:31 nigel
2002-06-10 10:21 Fco.J.Ballesteros
2002-06-10 10:10 forsyth
2002-06-07  9:35 nigel
2002-06-10  9:53 ` Blake McBride
2002-06-10 17:00   ` Steve Kilbane
2002-06-11  9:08   ` Don
2002-06-11 18:55     ` Vladimir G. Ivanovic
2002-06-12  8:54       ` Don
2002-06-11  9:09   ` Douglas A. Gwyn
2002-06-10 10:02 ` Douglas A. Gwyn
2002-06-10 14:10 ` Blake McBride
2002-06-10 17:13   ` Quinn Dunkan
2002-06-10 18:15     ` Fariborz Tavakkolian
2002-06-10 20:43   ` FJ Ballesteros
2002-06-11  9:08   ` Don
2002-06-11  9:09   ` Douglas A. Gwyn
2002-06-12  8:54   ` Joel Salomon
2002-06-10 15:47 ` James A. Robinson
2002-06-11 15:27 ` Blake McBride
2002-06-11 17:36   ` Digby Tarvin
2002-06-11 17:44     ` James A. Robinson
2002-06-11 20:43       ` Digby Tarvin
2002-06-07  9:06 Blake McBride

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=E17I53n-0001LI-00@minster.cs.york.ac.uk \
    --to=john@cs.york.ac.uk \
    --cc=9fans@cse.psu.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).