From: Richard <ru@ohio.river.org>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: interaction
Date: Tue, 18 Jul 2000 11:38:53 -0700 [thread overview]
Message-ID: <200007181838.LAA02161@ohio.river.org> (raw)
In-Reply-To: <200007180807.EAA19981@cse.psu.edu>
forsyth@caldo.demon.co.uk writes:
> Richard> do you 2 use it as your interactive shell, too, or just
> Richard> for scripts?
> in acme and rio i might have a window open on a file of
>common sequences for editing, snarfing and sending into shells and other
>commands. when developing in acme, i have the word mk typed in the tag
>of the directory window so that one click of a button will execute it
>and pop the diagnostics into another window for use by button 3. i can
>have different commands for different windows (adiff /one/thing
>/another/thing is a common one at the moment). furthermore, in all but
>the function case i can see what i need and get what i see, and they all
>handle multiline commands sensibly, which i've never found true for most
>`richard the third' interfaces.
those suggestions are specific to Plan 9 whereas I was asking the 2 posters
about their style of usage of rc on *Unix*.
it is always good, though, to recieve confirmation that experienced Plan
9 users actually follow the general style described in the Acme and
Plumber papers. and "see what I need and get what I see" is an apt
description of that style. per analogy with WYSIWYG, maybe we should
shorten it to SWYNAGWYS.
>in short, it's worth experimenting with the things the system gives you.
definitely.
prev parent reply other threads:[~2000-07-18 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-18 8:07 forsyth
2000-07-18 18:38 ` Richard [this message]
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=200007181838.LAA02161@ohio.river.org \
--to=ru@ohio.river.org \
--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).