From: Jeremy Fitzhardinge jeremy@sw.oz.au
Subject: 8-1/2 (was: Really about PLan 9)
Date: Mon, 4 Sep 1995 06:02:26 -0400 [thread overview]
Message-ID: <19950904100226.nrFRVxTKICKotcyCpC2WSwTWNCJtJmgi9RL4XzkQzfY@z> (raw)
In <425kho$524@booz.bah.com> jason@absolut.minerva.bah.COM (Jason Haynes) writes:
>For every day tasks I use pico,
>since it's quick and neat. For real editing tasks (programming, etc), I
>almost always use Sam. I only wish it had some ability for customization,
>at least some sort of alias/macro feature for storing commonly used regex.
It does:
; whatis S
fn S {sam $* $home/lib/sampad}
; cat lib/sampad
<collection of various useful commands and regexps, which I can cut'n'paste
into the command window, including some a little like the Emacs directory mode,
which munges the output of ls to make files easily accessible>
J
reply other threads:[~1995-09-04 10:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19950904100226.nrFRVxTKICKotcyCpC2WSwTWNCJtJmgi9RL4XzkQzfY@z \
--to=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).