From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: find-function-source-directory
Date: Mon, 19 Feb 2018 11:13:12 +0000 [thread overview]
Message-ID: <CAPM58ohNk_aufUKOyNSY2RwXJCtms0A9XQHe4U1+gKh8B97Srw@mail.gmail.com> (raw)
In-Reply-To: <83mv069jlp.fsf@gnu.org>
On 18 February 2018 at 19:35, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sun, 18 Feb 2018 20:40:50 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> (setq find-function-source-path
>> '("c:/projects/emacs/lisp/"
>> "c:/projects/emacs/lisp/emacs-lisp/"
>> "c:/projects/emacs/lisp/net/"
>> ...))
>>
>> (add more subdirectories instead of the ellipsis).
>
> This notwithstanding, I think that doc string is misleading: what you
> want to accomplish isn't possible, because find-function-source-path
> cannot override load-path in this use case. Or maybe I'm missing
> something.
Ah, thanks. (Sorry, I missed this message earlier.)
I'm wondering if there is there any use for
find-function-source-path, if not that. Perhaps it
is an ex-feature?
next prev parent reply other threads:[~2018-02-19 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 16:16 find-function-source-directory Richard Copley
2018-02-18 18:40 ` find-function-source-directory Eli Zaretskii
2018-02-18 19:35 ` find-function-source-directory Eli Zaretskii
2018-02-19 11:13 ` Richard Copley [this message]
2018-02-19 11:44 ` find-function-source-directory tomas
2018-02-19 15:36 ` find-function-source-directory Eli Zaretskii
2018-02-19 15:43 ` find-function-source-directory tomas
2018-02-18 19:53 ` find-function-source-directory Drew Adams
2018-02-18 20:18 ` find-function-source-directory Eli Zaretskii
[not found] ` <<a8455f40-e18a-44ac-8523-435e84f2d2e8@default>
[not found] ` <<83h8qe9hld.fsf@gnu.org>
2018-02-18 21:56 ` find-function-source-directory Drew Adams
2018-02-19 3:24 ` find-function-source-directory Richard Copley
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=CAPM58ohNk_aufUKOyNSY2RwXJCtms0A9XQHe4U1+gKh8B97Srw@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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 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.