From: Paul Eggert <eggert@cs.ucla.edu>
To: Emacs development discussions <emacs-devel@gnu.org>
Subject: Install C source code for for debugging help
Date: Thu, 26 Sep 2019 13:37:37 -0700 [thread overview]
Message-ID: <7ba0e94a-6256-c425-aaf8-7ee8822216a7@cs.ucla.edu> (raw)
In Bug#37527 I proposed a patch to let builders install a compressed
copy of the C source code for Emacs, so that when users type things like
'C-h f car RET' they get a button that takes them to the source code for
'car' instead of giving them a mysterious prompt like "Emacs C source
dir: ~/" (which is what I get on Debian).
This patch lets builders choose whether to install the compressed
source. The default is to install it, as the filesystem overhead of
installing the source code (about 2% of the typical install size) is
typically not worth worrying about; plus, there is value in encouraging
builders to better follow the free-software principle of making it easy
for users to study how Emacs works. Builders can also choose to not
install the source, or to have Emacs refer to place where the source was
located when Emacs was built (this last approach does not work in
typical GNU/Linux distributions, as the build location is not available
when Emacs is run).
If you run an uninstalled Emacs, it continues to refer to its C source
directory as before.
I'm mentioning this proposed patch on emacs-devel to see whether anyone
sees a problem with the idea before I install the patch.
next reply other threads:[~2019-09-26 20:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 20:37 Paul Eggert [this message]
2019-09-27 5:07 ` Install C source code for for debugging help Eli Zaretskii
2019-09-27 6:13 ` Paul Eggert
2019-09-27 7:19 ` Eli Zaretskii
2019-09-27 13:01 ` Stefan Monnier
2019-09-27 13:12 ` Stefan Monnier
2019-09-27 13:33 ` Eli Zaretskii
2019-09-27 13:48 ` Stefan Monnier
2019-09-27 13:56 ` Eli Zaretskii
2019-09-27 14:24 ` Paul Eggert
2019-09-27 14:40 ` Eli Zaretskii
2019-09-28 4:03 ` Paul Eggert
2019-09-27 17:04 ` Noam Postavsky
2019-09-27 22:45 ` Fu Yuan
2019-09-28 0:09 ` Juanma Barranquero
2019-09-28 2:14 ` Michael Rohleder
2019-09-27 15:25 ` Stefan Monnier
2019-09-28 1:32 ` Richard Stallman
2019-09-28 2:06 ` Jean-Christophe Helary
2019-09-27 15:03 ` Lars Ingebrigtsen
2019-09-27 15:47 ` David Ringo
2019-09-27 8:37 ` Andreas Schwab
2019-09-27 9:06 ` Eli Zaretskii
2019-09-27 11:58 ` Andreas Schwab
2019-09-27 12:58 ` Eli Zaretskii
2019-09-27 13:45 ` Andreas Schwab
2019-09-27 13:50 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-09-28 18:19 Angelo Graziosi
2019-09-29 6:56 ` Paul Eggert
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=7ba0e94a-6256-c425-aaf8-7ee8822216a7@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--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 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).