From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Installing the Emacs executable
Date: Wed, 24 Apr 2013 09:12:20 -0400 [thread overview]
Message-ID: <jwvvc7c2if2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <33A901B8-67E3-4C81-BF5B-7C9B4A8836E1@raeburn.org> (Ken Raeburn's message of "Wed, 24 Apr 2013 01:05:07 -0400")
>> That's a different issue. My question was about what "make install"
>> does with DOC, not what "make emacs" does in src. We can install DOC
>> under the name DOC-XX.YY.ZZ without changing what happens in src and
>> in etc of the build tree.
A simpler solution is to drop the DOC-XX.YY.ZZ and only use a single
"DOC" file. I've been doing that quite happily for years now.
> I've long wondered if it would be better to get rid of the DOC file
> altogether and keep the documentation in the executable image.
That could be an option. There are various ways this could be done, but
I think it would only be worth it if it can simplify the code.
Given the fact that we'd most likely still need to keep most of the
current code to lazy-load docstrings/bytecode from those .elc files that
are not preloaded, I think it'll be difficult to come up with something
that simplifies the code.
Stefan
next prev parent reply other threads:[~2013-04-24 13:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 16:32 Installing the Emacs executable Eli Zaretskii
2013-04-16 17:15 ` Andreas Schwab
2013-04-16 17:20 ` Glenn Morris
2013-04-16 18:11 ` Eli Zaretskii
2013-04-19 18:29 ` Andreas Schwab
2013-04-19 18:49 ` Eli Zaretskii
2013-04-19 18:57 ` Glenn Morris
2013-04-19 19:05 ` Eli Zaretskii
2013-04-19 19:08 ` Glenn Morris
2013-04-20 1:48 ` Stefan Monnier
2013-04-19 20:58 ` Andreas Schwab
2013-04-20 6:37 ` Eli Zaretskii
2013-04-20 10:44 ` Andreas Schwab
2013-04-20 10:56 ` Eli Zaretskii
2013-04-20 11:55 ` Andreas Schwab
2013-04-20 12:31 ` Eli Zaretskii
2013-04-20 13:24 ` Andreas Schwab
2013-04-20 15:43 ` Eli Zaretskii
2013-04-20 15:56 ` Andreas Schwab
2013-04-24 5:05 ` Ken Raeburn
2013-04-24 13:12 ` Stefan Monnier [this message]
2013-04-24 17:06 ` Eli Zaretskii
2013-04-24 18:54 ` Stefan Monnier
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=jwvvc7c2if2.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=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 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).