From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: [9fans] Re: interaction
Date: Tue, 18 Jul 2000 09:07:19 +0100 [thread overview]
Message-ID: <200007180807.EAA19981@cse.psu.edu> (raw)
Richard> do you 2 use it as your interactive shell, too, or just
Richard> for scripts?
when i expect to repeat or find i do repeat a particular sequence
of commands, rather than hunt in a transcript or type incantations to hunt them down,
i usually define a function or two (say `x') that encapsulates the sequence,
and use that. (it also has the advantage that i can squirt the definition into windows
open on distinct directories.) 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.
in short, it's worth experimenting with the things the system gives you.
next reply other threads:[~2000-07-18 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-18 8:07 forsyth [this message]
2000-07-18 18:38 ` Richard
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=200007180807.EAA19981@cse.psu.edu \
--to=forsyth@caldo.demon.co.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).