From: George Michaelson <ggm@algebras.org>
To: The Eunuchs Hysterical Society <TUHS@tuhs.org>
Subject: [TUHS] Re: emacs
Date: Sat, 5 Aug 2023 14:09:59 +1000 [thread overview]
Message-ID: <CAKr6gn2Wqz87=qAro_z4UstLLX9NLB6O7Pdr4G_dewYB_nKCaw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PHvpz4K1pr-fCSCcTOyVQo-jJLDAZ5jEM6W8dv8930Bg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Gosling Emacs had a very handy "make the following sequence of commands a
macro" feature which I used to do stupid fix ups to text files cross file.
Things like "find every line which starts with x.. back up two lines and
fix something else y and insert z, then save the file and go onto the next
one"
People laughed at me pointing to much better tools (spitbol?, sed?) But
sometimes the hammer you have smashes those delicate screws into the watch
case just beautifully quickly. If somewhat crudely.
I liked teco. It's in the freebsd ports tree as an uplift to c I believe.
G
[-- Attachment #2: Type: text/html, Size: 765 bytes --]
next prev parent reply other threads:[~2023-08-05 4:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 2:36 Noel Chiappa
2023-08-04 2:42 ` Rob Pike
2023-08-04 16:19 ` Clem Cole
2023-08-05 4:09 ` George Michaelson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-04 2:17 Noel Chiappa
2023-08-04 5:03 ` Jonathan Gray
2023-08-05 4:34 ` Jonathan Gray
2023-08-04 0:04 [TUHS] emacs Will Senn
2023-08-04 0:19 ` [TUHS] emacs Adam Thornton
2023-08-04 0:27 ` Rob Pike
2023-08-04 0:49 ` Larry McVoy
2023-08-04 1:00 ` Rich Salz
2023-08-04 13:25 ` Lars Brinkhoff
2023-08-04 0:32 ` Warner Losh
2023-08-04 1:23 ` Larry Stewart
2023-08-04 13:38 ` Ronald Natalie
2023-08-04 1:59 ` Will Senn
2023-08-04 2:26 ` Erik E. Fair
2023-08-04 0:39 ` Greg 'groggy' Lehey
2023-08-04 0:44 ` Clem Cole
2023-08-04 0:47 ` Clem Cole
2023-08-04 0:53 ` Warner Losh
2023-08-04 2:14 ` Dan Halbert
2023-08-04 2:18 ` Bakul Shah
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='CAKr6gn2Wqz87=qAro_z4UstLLX9NLB6O7Pdr4G_dewYB_nKCaw@mail.gmail.com' \
--to=ggm@algebras.org \
--cc=TUHS@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).