unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org,  all_but_last@163.com,  emacs-devel@gnu.org
Subject: Re: Undocumented elisp_type_hierarchy.{jpg|txt} in info directory.
Date: Sat, 06 Apr 2024 22:57:37 +0200	[thread overview]
Message-ID: <87le5q9pku.fsf@gmx.net> (raw)
In-Reply-To: <86a5m63903.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Apr 2024 16:39:56 +0300")

On Sat, 06 Apr 2024 16:39:56 +0300 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: rms@gnu.org,  all_but_last@163.com,  emacs-devel@gnu.org
>> Date: Sat, 06 Apr 2024 13:39:20 +0200
>>
>> On Sat, 06 Apr 2024 09:45:19 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> >> From: Richard Stallman <rms@gnu.org>
>> >> Cc: all_but_last@163.com, emacs-devel@gnu.org
>> >> Date: Fri, 05 Apr 2024 17:41:19 -0400
>> >>
>> >>   > This is incorrect.  Info manuals can include images, for those Info
>> >>   > readers which (like Emacs) are capable of displaying images.  See the
>> >>   > node "Images" in the Texinfo manual.
>> >>
>> >> Do we publish any text about this issue
>> >> that we should update?
>> >
>> > If you mean in files like INSTALL in our distribution, or in some
>> > other GNU manuals, then no, I don't think we should update anything.
>>
>> Should INSTALL say anything about native compilation, e.g. that it
>> requires libgccjit, which Emacs uses by default if present, otherwise
>> configure with --with-native-compilation=no to build without it?  If so,
>> then should section 6 under DETAILED BUILDING AND INSTALLATION also
>> refer to the sibling directory ../native-lisp?
>>
>> Beyond these possible updates, it might be helpful to augment section 6
>> to point out the following differences between in-tree and out-of-tree
>> builds (since section 3b refers to building "in a separate directory"):
>> When executing src/emacs in-place in an out-of-tree build, it uses the
>> top-level lisp and info directories of the source directory, not of the
>> build directory, but it uses the lib-src and native-lisp directories of
>> the build directory.
>
> Is this relevant to the issue discussed in this thread?
>
> If you want to suggest additions and changes to INSTALL, feel free,
> but please start a new thread about that.  This one is about a very
> specific aspect of the Emacs installation: image files used by our
> manuals.

Oops, my eye just focussed on "I don't think we should update anything"
and disregarded the Subject line; sorry.  I've now proposed a patch in
bug#70246.

Steve Berman



      reply	other threads:[~2024-04-06 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  8:13 Undocumented elisp_type_hierarchy.{jpg|txt} in info directory Zhu Zihao
2024-04-03 11:38 ` 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 [this message]

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=87le5q9pku.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=all_but_last@163.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).