From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: missing src/ directory for eval.c
Date: Mon, 11 Feb 2019 20:51:09 +0000 [thread overview]
Message-ID: <87zhr26oci.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <jwvbm3is9eg.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 11 Feb 2019 09:13:22 -0500)
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Unlike the Lisp files, the C files are not targeted and placed outside of
>> the source distribution by `make install`. It seems.
>
> Indeed, the C source files are not expected to be present in an
> Emacs installation. They're only expected to be present on the machine
> where Emacs was compiled.
>
> Part of the idea is that, if you're not compiling Emacs yourself,
> accessing the C source code is much less useful.
I think it would be useful if the help buffer explained this.
E.g.
"forward-char is an interactive built-in function in `C source code'.
C-source codes isn't usually available unless Emacs was installed from
source."
BR,
Robert Thorpe
next prev parent reply other threads:[~2019-02-11 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 11:35 missing src/ directory for eval.c (Was: 1L?) Van Ly
2019-02-11 13:03 ` tomas
2019-02-11 13:56 ` Noam Postavsky
2019-02-11 14:13 ` missing src/ directory for eval.c Stefan Monnier
2019-02-11 15:16 ` Michael Albinus
2019-02-11 16:44 ` tomas
2019-02-11 20:51 ` Robert Thorpe [this message]
2019-02-11 20:54 ` Emanuel Berg
2019-02-11 22:11 ` Stefan Monnier
2019-02-12 0:01 ` Emanuel Berg
2019-02-12 4:00 ` Stefan Monnier
2019-02-12 5:16 ` Emanuel Berg
2019-02-11 14:17 ` missing src/ directory for eval.c (Was: 1L?) Yuri Khan
2019-02-11 20:45 ` Emanuel Berg
2019-02-11 22:01 ` Van L
2019-02-12 0:04 ` Emanuel Berg
2019-02-12 12:21 ` missing src/ directory for eval.c Van L
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=87zhr26oci.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.