all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Zhu Zihao <all_but_last@163.com>
To: emacs-devel@gnu.org
Subject: Undocumented elisp_type_hierarchy.{jpg|txt} in info directory.
Date: Wed, 03 Apr 2024 16:13:12 +0800	[thread overview]
Message-ID: <86ttkin96b.fsf@163.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]


Recently I checked my Emacs installation, and find two file named
elisp_type_hierarchy.{jpg|txt} in share/info directory(these two files
are placed in doc/lispref in source tree).

According to usual packaging convention, the share/info directory should
only contains compiled texinfo file (use 'info' as extension). It should
not contains txt or jpg (And I believe GNU info or other info reader
will ignore them).

One of my friend points me to a commit https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=415604c7a77205d91254a271f0112f69729eb3a9
In this commit, I found that emacs will use these two files to produce
info file. But IIRC, these source file should not be copied into the
destination of info file, they'll be contained in the compiled info.

Can someone tell me that it's purposed to do so, or just unintentional?
thanks! 
-- 
Retrieve my PGP public key:

  gpg --recv-keys B3EBC086AB0EBC0F45E0B4D433DB374BCEE4D9DC

Zihao

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

             reply	other threads:[~2024-04-03  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  8:13 Zhu Zihao [this message]
2024-04-03 11:38 ` Undocumented elisp_type_hierarchy.{jpg|txt} in info directory Eli Zaretskii
2024-04-05 21:41   ` Richard Stallman
2024-04-06  6:45     ` Eli Zaretskii
2024-04-06 11:39       ` Stephen Berman
2024-04-06 13:39         ` Eli Zaretskii
2024-04-06 20:57           ` Stephen Berman

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=86ttkin96b.fsf@163.com \
    --to=all_but_last@163.com \
    --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 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.