From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: emacs-devel@gnu.org
Subject: Re: Not using DOC for ELisp files
Date: Mon, 03 Jan 2022 16:30:58 +0200 [thread overview]
Message-ID: <838rvwdh7h.fsf@gnu.org> (raw)
In-Reply-To: <30e03635-843d-f3be-7709-d4b633b2c90a@raeburn.org> (message from Ken Raeburn on Mon, 3 Jan 2022 08:48:03 -0500)
> Date: Mon, 3 Jan 2022 08:48:03 -0500
> From: Ken Raeburn <raeburn@raeburn.org>
>
> Another piece I recall looking at, which I don't remember if I brought
> up on the list at the time, was moving the C based doc strings into the
> generated .o files and the executable
Did you only think about ELF executables, or did you consider how to
do this with any binary formats we support?
next prev parent reply other threads:[~2022-01-03 14:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 1:48 Not using DOC for ELisp files Stefan Monnier
2021-12-28 2:25 ` Po Lu
2021-12-28 3:48 ` Stefan Kangas
2021-12-28 5:39 ` Po Lu
2021-12-28 4:11 ` LdBeth
2021-12-28 5:03 ` Stefan Monnier
2021-12-28 5:38 ` Po Lu
2021-12-28 9:52 ` Phil Sainty
2021-12-28 10:31 ` Po Lu
2021-12-28 12:47 ` Po Lu
2021-12-28 7:10 ` Lars Ingebrigtsen
2021-12-28 3:39 ` Stefan Kangas
2021-12-28 5:10 ` Stefan Monnier
2021-12-28 6:56 ` Lars Ingebrigtsen
2021-12-28 12:44 ` Eli Zaretskii
2021-12-28 17:14 ` Stefan Monnier
2021-12-28 18:17 ` Eli Zaretskii
2021-12-29 0:15 ` Stefan Monnier
2021-12-29 12:30 ` Johann Klähn
2021-12-29 23:08 ` Stefan Monnier
2021-12-29 12:52 ` Eli Zaretskii
2021-12-29 23:23 ` Stefan Monnier
2021-12-30 7:20 ` Eli Zaretskii
2021-12-31 4:19 ` Stefan Monnier
2021-12-31 8:57 ` Eli Zaretskii
2021-12-31 16:16 ` Stefan Monnier
2021-12-31 18:45 ` Eli Zaretskii
2022-01-03 13:48 ` Ken Raeburn
2022-01-03 14:30 ` Eli Zaretskii [this message]
2022-01-07 22:59 ` Ken Raeburn
2022-01-08 7:08 ` Eli Zaretskii
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=838rvwdh7h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raeburn@raeburn.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 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.