From: Jan Schaumann via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Dot (graphviz) to ascii
Date: Tue, 18 Jan 2022 08:13:54 -0500 [thread overview]
Message-ID: <20220118131354.GB6133@netmeister.org> (raw)
In-Reply-To: <20220118125348.GA6133@netmeister.org>
Jan Schaumann via TUHS <tuhs@minnie.tuhs.org> wrote:
> Richard Salz <rich.salz@gmail.com> wrote:
> > >From Thomas Ptacek on twitter [1], quoting something on HackerNews [2]: a
> > person wrote a dot-file renderer for ASCII diagrams [3] It seems to be a
> > service; source not available.
>
> The source appears to be here:
> https://github.com/ggerganov/dot-to-ascii
Sorry, OT, I guess, just wanted to follow up with the
link to what does the actual heavy lifting, and as so
often, the answer is Perl:
https://metacpan.org/pod/Graph::Easy
-Jan
prev parent reply other threads:[~2022-01-18 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 12:49 Richard Salz
2022-01-18 12:53 ` Jan Schaumann via TUHS
2022-01-18 13:13 ` Jan Schaumann via TUHS [this message]
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=20220118131354.GB6133@netmeister.org \
--to=tuhs@minnie.tuhs.org \
--cc=jschauma@netmeister.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).