9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lee Fallat <ircsurfer33@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] problem with acme on 9front
Date: Thu, 19 May 2016 16:37:43 -0400	[thread overview]
Message-ID: <CAKzHxzFp_y4mu8muL9vZNPGhq93j+ROxn+E6egE56UYwC=+SiA@mail.gmail.com> (raw)
In-Reply-To: <CAK-yzPOLfUw4V0u_ifY=wPgs4_2bPQiKe_Huof64s869xZ3vJg@mail.gmail.com>

>From experience, Sam's command window provides a more consistent
experience with the rest of the system. Acme on the other hand
pretends to have individual command windows (more like command lines)
for every file open. Sam has some form of "tiling", but not as
automatic as Acme. Sam also has a remote editing protocol, unlike
Acme. I liked Sam not only for those reasons, but also because of what
Charles said - you can script Sam with sam -d, allowing it to
integrate into other parts of the system.

It's too bad there has not been a clean rewrite of Sam, like Rob has
mentioned in his paper.

On Thu, May 19, 2016 at 4:26 PM, Mark Lee Smith <netytan@gmail.com> wrote:
> I'm was merely explaining my understanding of the context so that I could be
> corrected if I was wrong on any point. I didn't mean to explain Acme to you.
> While I replied to you (I believe I did), please understand my question in
> the light of the thread, as it were, a whole.
>
> Thanks, everyone, for the answers!
>
>
> On Thu, 19 May 2016 at 21:38 <cinap_lenrek@felloff.net> wrote:
>>
>> mark, why do you explain acme to me?
>>
>> --
>> cinap
>>
>



  reply	other threads:[~2016-05-19 20:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 18:30 christophe DAMAS
2016-05-19 18:40 ` Siarhei Zirukin
2016-05-19 19:42   ` Charles Forsyth
2016-05-19 21:51     ` Kurt H Maier
2016-05-20  0:37       ` Lyndon Nerenberg
2016-05-20  1:23         ` Ethan Grammatikidis
2016-05-20  1:32           ` Lyndon Nerenberg
2016-05-20  2:02             ` Ethan Grammatikidis
2016-05-20  2:07               ` Lyndon Nerenberg
2016-05-20 11:58                 ` hiro
2016-05-20 12:07                   ` Mark van Atten
2016-05-20 15:49                     ` Wes Kussmaul
2016-05-20 12:12                   ` Brantley Coile
2016-05-20 20:01                 ` Steve Simon
2016-05-21 21:52                   ` Mark Lee Smith
2016-05-21 23:18                     ` erik quanstrom
2016-05-22  7:36                     ` Siarhei Zirukin
2016-05-22 17:28                       ` Mark Lee Smith
2016-05-21 17:36       ` erik quanstrom
2016-05-21 18:16         ` Kurt H Maier
2016-05-21 18:28           ` Rob Pike
2016-05-21 19:21             ` Kurt H Maier
2016-05-21 23:14           ` Lyndon Nerenberg
2016-05-19 18:41 ` cinap_lenrek
2016-05-19 19:20   ` Mark Lee Smith
2016-05-19 19:36     ` cinap_lenrek
2016-05-19 20:26       ` Mark Lee Smith
2016-05-19 20:37         ` Lee Fallat [this message]
2016-05-19 20:40         ` Aram Hăvărneanu
2016-05-19 20:11     ` stanley lieber
2016-05-19 20:15       ` Charles Forsyth
2016-05-19 20:53         ` stanley lieber
2016-05-19 21:13           ` Mark van Atten
2016-05-19 21:18             ` Lee Fallat
2016-05-21 19:08               ` Mark van Atten
2016-05-21 19:23 trebol55555

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='CAKzHxzFp_y4mu8muL9vZNPGhq93j+ROxn+E6egE56UYwC=+SiA@mail.gmail.com' \
    --to=ircsurfer33@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).