From: Andrea Corallo <acorallo@gnu.org>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, stefankangas@gmail.com
Subject: Re: Emacs object type hierarchy
Date: Thu, 15 Feb 2024 12:40:56 -0500 [thread overview]
Message-ID: <yp17cj5bp7b.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <yp1bk8hbpsb.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Thu, 15 Feb 2024 12:28:20 -0500")
Andrea Corallo <acorallo@gnu.org> writes:
> Hello all,
>
> back on this subject.
>
> I've pushed on feature/type-hierarchy a branch that does the following
> things:
>
> - Define the type hierarchy for builtin types with `cl--type-hierarchy'
> and generates automatically `cl--typeof-types' from it. The format of
> `cl--type-hierarchy' is I believe more compact and less error prone.
>
> - Generates automatically a graphical and textual representation of the
> type hierarchy using etc/syncdoc-type-hierarchy.el. (This relies on
> graphviz and graph-easy which AFAIU are both Free Software)
>
> - Add an initial "Type Hierarchy" under "Lisp Data Types" in the elisp
> manual.
>
> - Include the generated representation of the type hierarchy in it.
>
> Here [1] the current image it renders of the hierarchy.
>
> There are still edges that needs to be rounded but I wanted to share it
> in order to collect some feedback.
>
> Thanks!
>
> Andrea
>
> [1] <https://git.savannah.gnu.org/cgit/emacs.git/plain/doc/lispref/type_hierarchy.jpg?h=feature/type-hierarchy>
One thing I forgot to mention I'm not very satisfied of.
Unfortunatelly the textual represantation in ascii art does not render
very well on a regular terminal size unless trucate-lines is null.
Maybe a simple table would be just a better option for text? Of the
tools I tried graph-easy is IME the one I managed to produced the best
output already.
Thanks
Andrea
next prev parent reply other threads:[~2024-02-15 17:40 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
2024-02-15 17:28 ` Andrea Corallo
2024-02-15 17:40 ` Andrea Corallo [this message]
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=yp17cj5bp7b.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/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).