From: "James A. Robinson" <jimr@highwire.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Musings on Interfaces
Date: Thu, 1 Sep 2016 15:59:04 +0000 [thread overview]
Message-ID: <CAPd04b7CBS-zCR2yOWMt5grLtucYZb=38JsnWB4G-iaa2=0Kug@mail.gmail.com> (raw)
In-Reply-To: <9A3455DB-8B65-46B3-9F57-6E98639392CB@me.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
I used to use sam exclusively on my Linux machine. I had to stop after I
switched to Mac OS X many years ago.
A few years later I picked up acme, and have been using it since. I also
find that, for some reason I can't explain, I have rarely reached for the
Edit X// command in a scratch window. I really ought to use it more
often, it's not *that* much different than the sam command window, and I
naturally made very heavy use of the sam command language when I was using
sam(1) all the time. For some reason in my head there is a tiny barrier
between using Edit X// vs. selecting a window in sam and then using the
command window.
The one thing I always miss from sam is the remote editor ability. Given
sam + ssh it was really a joy to be able to remote edit files, much nicer
than using the remote editing capability of emacs. I had plumber rules set
up so that I could use a remote 'B' command to trigger opening the files
from the remote machine, and it was very nice to seamlessly navigate and
edit w/o really thinking about where the file was.
Jim
[-- Attachment #2: Type: text/html, Size: 1497 bytes --]
next prev parent reply other threads:[~2016-09-01 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 14:42 Brantley Coile
2016-09-01 15:40 ` Bakul Shah
2016-09-01 16:05 ` Mark van Atten
2016-09-01 17:20 ` James A. Robinson
2016-09-01 19:10 ` Mark van Atten
2016-09-01 22:15 ` Travis Moore
2016-09-01 15:59 ` James A. Robinson [this message]
2016-09-01 16:36 ` Adriano Verardo
2016-09-01 17:54 ` Brantley Coile
2016-09-01 18:05 ` arnold
2016-09-01 22:56 ` Winston Kodogo
2016-09-02 1:52 ` Winston Kodogo
2016-09-02 9:06 ` cinap_lenrek
2016-09-02 14:19 ` Steven Stallion
2016-09-02 15:37 ` Kurt H Maier
2016-09-02 6:10 ` Mart Zirnask
2016-09-02 7:34 ` Steve Simon
2016-09-02 7:59 ` Ole-Hjalmar Kristensen
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='CAPd04b7CBS-zCR2yOWMt5grLtucYZb=38JsnWB4G-iaa2=0Kug@mail.gmail.com' \
--to=jimr@highwire.org \
--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).