From: magma698hfsp273p9f@icebubble.org
To: 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Mon, 03 Aug 2020 18:50:38 +0000 [thread overview]
Message-ID: <86pn877edd.fsf@cmarib.ramside> (raw)
In-Reply-To: <21d509a3-0f9f-4f08-bdf6-1a2c73ccea07@www.fastmail.com> (Ethan Gardener's message of "Fri, 31 Jul 2020 11:59:01 +0100")
"Ethan Gardener" <eekee57@fastmail.fm> writes:
> you know, the above point may be directly applicable to using scms
> with their arcane things to remember on top of the code you're
> writing. however, it's definitely directly applicable to coming up
> with analysis scripts for dump or wikifs. (despite plan 9's lovely
> unified regexps.) which is the lesser evil? don't ask me, i'm trying
> to develop something better than either. :}
Why would you object to anyone doing a text search on the docs? That
seems like it would be a very convenient benefit of having text-based
documentation in a unified tree. Plan 9's intentional choice to use
text-based mechanisms no doubt anticipated synergies such as this. I
don't know about you, but I regularly search my mailbox files using
grep. That's one of the reasons why I chose a MUA which stores messages
in plain text. They're more useful, that way.
next prev parent reply other threads:[~2020-08-03 19:14 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 9:09 sirjofri+ml-9front
2020-07-27 9:56 ` [9front] " hiro
2020-07-27 15:10 ` Amavect
2020-07-27 15:54 ` Stanley Lieber
2020-07-27 15:58 ` ori
2020-07-27 17:01 ` William Gunnells
2020-07-27 17:29 ` Stanley Lieber
2020-07-27 18:09 ` William Gunnells
2020-07-27 20:01 ` ori
2020-07-27 21:22 ` Ethan Gardener
2020-07-28 19:10 ` cinap_lenrek
2020-07-29 22:36 ` Ethan Gardener
2020-07-27 22:06 ` Anthony Martin
2020-07-27 22:21 ` Stanley Lieber
2020-07-27 23:46 ` ori
2020-07-27 22:17 ` Stanley Lieber
2020-07-27 22:47 ` Kurt H Maier
2020-07-27 23:50 ` ori
2020-07-28 4:56 ` sirjofri+ml-9front
2020-07-28 10:18 ` hiro
2020-07-28 11:27 ` sirjofri+ml-9front
2020-07-28 12:14 ` hiro
2020-07-28 13:08 ` sirjofri+ml-9front
2020-07-28 14:16 ` hiro
2020-07-28 15:01 ` Stanley Lieber
2020-07-28 15:12 ` ori
2020-07-28 15:46 ` Stanley Lieber
2020-07-28 17:25 ` hiro
2020-07-28 17:37 ` ori
2020-07-28 17:43 ` Kurt H Maier
2020-07-28 15:11 ` ori
2020-07-28 11:29 ` sirjofri+ml-9front
2020-07-29 17:10 ` ori
2020-07-30 1:02 ` sl
2020-07-28 9:48 ` hiro
2020-07-30 18:12 ` magma698hfsp273p9f
2020-07-30 18:48 ` kvik
2020-07-30 18:54 ` ori
2020-07-30 19:28 ` Eckard Brauer
2020-07-30 19:59 ` Romano
2020-07-31 13:44 ` kvik
2020-07-31 13:51 ` Stanley Lieber
2020-08-01 15:42 ` Ethan Gardener
2020-07-30 19:15 ` Kurt H Maier
2020-07-31 10:59 ` Ethan Gardener
2020-08-03 18:50 ` magma698hfsp273p9f [this message]
2020-08-04 17:13 ` Ethan Gardener
[not found] <98A6B5A900B5E1660221CE63074D0920@ewsd.inri.net>
2020-07-30 2:14 ` ori
2020-07-30 3:06 ` Stanley Lieber
2020-07-30 3:12 ` Michael Misch
2020-07-30 8:19 ` hiro
2020-07-30 8:58 ` Kurt H Maier
2020-07-30 12:03 ` Ethan Gardener
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=86pn877edd.fsf@cmarib.ramside \
--to=magma698hfsp273p9f@icebubble.org \
--cc=9front@9front.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).