From: Richard Stallman <rms@gnu.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: find-function-C-source-directory
Date: Sun, 28 May 2006 14:19:21 -0400 [thread overview]
Message-ID: <E1FkPrF-00069N-JJ@fencepost.gnu.org> (raw)
In-Reply-To: <44796BD8.1030304@student.lu.se> (message from Lennart Borgman on Sun, 28 May 2006 11:22:32 +0200)
> I assume you are talking about users that do have the sources on their
> machine, so the only problem is that the source directory is not what
> is recorded in the binary. If so, the only problem I know of is that
> they need to type in the directory where they have the sources, only
> once per session, when Emacs prompts for it.
>
Yes, that is correct. The problem is how they should find out that.
Where is that information? I think that it should be there right when
they try to access the C sources from within help. And possibly
somewhere in the manual too.
If they didn't build Emacs from sources, but they have copied the sources,
they must have done so manually. Emacs has no way of knowing where those
sources are. Only the user would know.
next prev parent reply other threads:[~2006-05-28 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 21:50 find-function-C-source-directory Lennart Borgman
2006-05-28 3:05 ` find-function-C-source-directory Eli Zaretskii
2006-05-28 9:22 ` find-function-C-source-directory Lennart Borgman
2006-05-28 18:19 ` Richard Stallman [this message]
2006-05-28 19:07 ` find-function-C-source-directory Lennart Borgman
2006-05-28 20:26 ` find-function-C-source-directory Eli Zaretskii
2006-05-28 22:20 ` find-function-C-source-directory Lennart Borgman
2006-05-29 3:33 ` find-function-C-source-directory Eli Zaretskii
2006-05-29 5:37 ` find-function-C-source-directory Lennart Borgman
2006-05-28 3:18 ` find-function-C-source-directory Richard Stallman
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=E1FkPrF-00069N-JJ@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--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).