Computer Old Farts Forum
 help / color / mirror / Atom feed
From: ralph at inputplus.co.uk (Ralph Corderoy)
Subject: [COFF] Other OSes?
Date: Thu, 05 Jul 2018 23:38:41 +0100	[thread overview]
Message-ID: <20180705223841.959CC21EC8@orac.inputplus.co.uk> (raw)
In-Reply-To: <82df833ae2a587b386b4154fc6051356a3510b19@webmail.yaccman.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

Hi Steve,

> With the advent of glass teletypes, [editor] scripts simply evaporated
> -- there was no equivalent.  (yes, there were programs like sed, but
> it wasn't the same...).  Changing, e.g., a function name oin 10 files
> got a lot more tedious.

I still write the odd editor script.  I interact with ed every day; it's
handy when the information for the edit is on the TTY from previous
commands and you just want to get in, edit, and w, q.

A shell script and ed script I use a lot is ~/bin/rcsanno, a `blame' for
RCS files that I have dotted about.  RCS because SCCS wasn't available
back before CSSC came along.

I runs through each revision on the path I'm interested in, e.g. 1.1 to
the latest 1.42.  It starts with 1.1, but with `1,1:' prepended to each
line.  For 1.2 onwards it does an rcsdiff(1) with `-e': produce an ed
script.  This is piped into a brief bit of awk that munges the ed script
to prepend the revision to any added or changed line, and then it's fed
into ed.  Thus the `1.2' that's created has all lines match /^1\.[12]:/.
And so on up to 1.42.  It's not the quickest way compared to
interpreting the RCS `,v' file, but it required no insight into that
file format and is `good enough'.

I suspect a more interesting question is what did Unix adopt from other
OSes that it would have been better without!  :-)

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


  parent reply	other threads:[~2018-07-05 22:38 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  5:56 wkt
2018-07-05  6:29 ` spedraja
2018-07-05  6:40 ` bakul
2018-07-05 15:23   ` clemc
2018-07-05 20:49     ` scj
2018-07-05 21:25       ` david
2018-07-06 15:42         ` gtaylor
2018-07-05 22:38       ` ralph [this message]
2018-07-05 23:11       ` bakul
2018-07-06  0:06         ` lm
2018-07-06 15:49           ` gtaylor
2018-07-06  0:52       ` tytso
2018-07-06  5:59         ` ralph
2018-07-06 15:59           ` gtaylor
2018-07-06 16:10             ` ralph
2018-07-06 16:47               ` gtaylor
2018-07-06 15:57         ` gtaylor
2018-07-06 15:38       ` gtaylor
2018-07-09  1:56         ` tytso
2018-07-09  3:25           ` gtaylor
2018-07-09  3:35             ` crossd
2018-07-09  3:43               ` gtaylor
2018-07-09  3:52                 ` imp
2018-07-09 11:32                   ` perry
2018-07-09 11:50                     ` perry
2018-07-09 11:34                 ` crossd
2018-07-09  5:23             ` tytso
2018-07-09 12:52               ` clemc
2018-07-09 13:06                 ` [COFF] PiDP Obsolesces Guaranteed clemc
2018-07-09 14:39                 ` [COFF] Other OSes? tytso
2018-07-09 14:46                   ` clemc
2018-07-09 11:24           ` perry
2018-07-05 22:51   ` ewayte
2018-07-08 20:31   ` perry
2018-07-08 20:53     ` perry
2018-07-09  2:44     ` crossd
2018-07-10  5:30       ` bakul
2018-07-16 14:49         ` crossd
2018-07-16 16:59           ` [COFF] Capabilities (was " bakul
2018-07-06  0:55 ` [COFF] " crossd
2018-07-06  5:42   ` bakul
2018-07-09  2:51     ` crossd
2018-07-10  5:41       ` bakul
2018-07-06  4:04 ` grog
2018-07-06 16:10   ` gtaylor
2018-07-06 18:27     ` [COFF] Editor Scripts scj
2018-07-06 19:04       ` gtaylor
2018-07-08 20:50 ` [COFF] Other OSes? perry
2018-07-08 23:27   ` bakul
2018-07-09  0:00     ` grog
2018-07-09  0:13       ` perry
2018-07-09  0:05     ` crossd
2018-07-09  0:56       ` lm
2018-07-09  2:23         ` crossd
2018-07-09  0:11     ` perry
2018-07-09  0:19       ` crossd
2018-07-09  2:00         ` bakul
2018-07-09  3:02           ` [COFF] Origination of awful security design [COFF, COFF] bill
2018-07-09 13:10           ` [COFF] Other OSes? david
2018-07-09 13:17           ` perry
2018-07-09 13:13         ` perry

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=20180705223841.959CC21EC8@orac.inputplus.co.uk \
    --to=coff@minnie.tuhs.org \
    /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).