From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] question about how twig was handled in Plan 9
Date: Thu, 04 Apr 2024 16:56:19 -0400 [thread overview]
Message-ID: <D5D7ACBAAEBA830E5738389C85FEA4EB@eigenstate.org> (raw)
In-Reply-To: <CAOMU-W2oE6hBz-N=ffA49L9SYeTHvL9nLeDfPJ87gWA-qm_7fQ@mail.gmail.com>
Quoth Mon Aaraj <mon.aaraj815@gmail.com>:
> This is a blind shot because I couldn't find other resources nor the
> code for the ``twig`` utility that was shipped with Plan 9 1st Ed. It
> would be preferable to find the source code.
>
> The part where identifying matches is apparently easy, but how do they
> then process it as though it conforms to a grammar?
https://github.com/Plan9-Archive/plan9-1e/tree/master/sys/src/cmd/twig
also described in detail here:
https://dl.acm.org/doi/pdf/10.1145/69558.75700
next prev parent reply other threads:[~2024-04-04 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 20:42 Mon Aaraj
2024-04-04 20:56 ` ori [this message]
2024-04-06 20:01 ` Dave Woodman
2024-04-04 20:58 ` Sigrid Solveig Haflínudóttir
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=D5D7ACBAAEBA830E5738389C85FEA4EB@eigenstate.org \
--to=ori@eigenstate.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).