all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org,  stefankangas@gmail.com
Subject: Re: Emacs object type hierarchy
Date: Tue, 24 Oct 2023 05:21:26 -0400	[thread overview]
Message-ID: <yp1a5s8jrzd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83y1ftmje7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Oct 2023 18:46:24 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefankangas@gmail.com>
>> Date: Mon, 23 Oct 2023 11:20:51 -0400
>> 
>> any comment on where would be more appropriate to document our type
>> hierarchy in the manual?
>
> Somewhere under "Lisp Data Types", I guess?
>
>> I'd like to give it a go on writing some documentation 😮😬 (I'll
>> probably need some support).
>
> Help in writing documentation is always available, don't worry about
> that.

Thanks 🙏, dumb question: do we have a way to include images into the
manual?

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.

Bests

  Andrea



  reply	other threads:[~2023-10-24  9:21 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yp1a5s8jrzd.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.