From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: Emacs object type hierarchy
Date: Tue, 24 Oct 2023 14:53:53 +0200 [thread overview]
Message-ID: <87fs20kwpq.fsf@dataswamp.org> (raw)
In-Reply-To: yp15y2wjkih.fsf@fencepost.gnu.org
Andrea Corallo wrote:
>>> Alternatively WDYT is the best way to include a graph
>>> similar to the one linked in my original message? I tried
>>> a couple of ways in order to render it to ascii but I'm
>>> not satisfied with the result so far.
>>
>> ASCII art will be needed anyway, as it is the fallback for
>> non-GUI terminals. But you can include images for those
>> terminals that support it. See, for example, the Gawk
>> manual, in the "Extension Mechanism Outline" node.
>
> Wonderful thanks for the info
What happens if you add to or change that list of type
relations, are you going to manually redraw the ASCII art
as well to keep in synch?
Maybe there is some package that can draw it for you, and
then again upon change?
Of all the ASCII art one can draw, this should be a very
simple box diagram? Org mode?
<+sth> \ \ . .- .
<+sth> . | \ |
<+sth> \__ \ | | / . . +
<+sth> \ | / / |
<+sth> ___ \| | | / __--' .
<+sth> '-_\ \ \ | :__ The
<+sth> ''-__ / _-'`` '- Swamplands
<+sth> ____ \ \ | /___,---''`
<+sth> ___ \ \ | | __:_.-'''`-
<+sth> : \| | | / ``-.
<+sth> \ | | |
<+sth> \ \ \ | / \ / \ /
<+sth> . | | || \ | / | / \ |/ \ / / \ \ . .
<+sth> | | || \ ||/ ||/ / |\| ||/ /| \ | \ / \ |/
<+sth> ____ / / | || __ \|/ \|/|/ ___ | \/ ||/ \ ____ \| |/| /||
<+sth> | | | | \ \|/ __ \ / |/ ||/
<+sth> ___ | | / \ | ____ _______ ___ |/
<+sth> | | | | || __ _______ __ ______
<+sth> _ _/ | | | || ___ _____ _____ ___
<+sth> / / / \ | \ ________ ___
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-10-24 12:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 8:44 Emacs object type hierarchy Andrea Corallo
2023-10-22 9:08 ` Gerd Möllmann
2023-10-22 9:37 ` Gerd Möllmann
2023-10-23 15:08 ` Andrea Corallo
2023-10-23 16:36 ` Gerd Möllmann
2023-10-23 16:48 ` Gerd Möllmann
2023-10-24 8:28 ` Andrea Corallo
2023-10-22 16:11 ` [External] : " Drew Adams
2023-10-24 0:57 ` Richard Stallman
2023-10-24 2:03 ` Emanuel Berg
2023-10-24 8:39 ` Andrea Corallo
2023-10-24 9:32 ` Emanuel Berg
2023-10-22 22:08 ` Yuan Fu
2023-10-23 15:06 ` Andrea Corallo
2023-10-23 15:49 ` John Yates
2023-10-24 3:37 ` Yuan Fu
2023-10-23 15:20 ` Andrea Corallo
2023-10-23 15:46 ` Eli Zaretskii
2023-10-24 9:21 ` Andrea Corallo
2023-10-24 11:55 ` Eli Zaretskii
2023-10-24 12:02 ` Andrea Corallo
2023-10-24 12:53 ` Emanuel Berg [this message]
2024-02-15 17:28 ` Andrea Corallo
2024-02-15 17:40 ` Andrea Corallo
2024-02-17 9:04 ` Emanuel Berg
2024-02-18 19:25 ` Andrea Corallo
2024-02-17 9:19 ` Eli Zaretskii
2024-02-17 9:38 ` Emanuel Berg
2024-02-17 9:41 ` Emanuel Berg
2024-02-18 19:23 ` Andrea Corallo
2024-02-18 19:33 ` Eli Zaretskii
2024-02-18 19:37 ` Eli Zaretskii
2024-02-19 7:52 ` Andrea Corallo
2024-02-19 16:51 ` Andrea Corallo
2024-02-26 17:50 ` Andrea Corallo
2024-03-01 8:36 ` Andrea Corallo
2024-03-01 8:56 ` Eli Zaretskii
2024-03-01 9:46 ` Andrea Corallo
2024-02-16 20:31 ` Basil L. Contovounesios
2024-02-18 19:14 ` Andrea Corallo
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs20kwpq.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).