Re: find-function-source-directory

[tomas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 19, 2018 at 11:13:12AM +0000, Richard Copley wrote:
> 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?


Hm. Looking at the elisp sources, it seems to me that this variable
is used (cf. find-library-name) in a way that corresponds with its
docstring. An extract:

  (defun find-library-name (library)
    "Return the absolute file name of the Emacs Lisp source of LIBRARY.
  LIBRARY should be a string (the name of the library)."
    ;; If the library is byte-compiled, try to find a source library by
    ;; the same name.
    (when (string-match "\\.el\\(c\\(\\..*\\)?\\)\\'" library)
      (setq library (replace-match "" t t library)))
    (or
     (locate-file library
                  (or find-function-source-path load-path)
                  (find-library-suffixes))
    [...]

So definitely not an ex-feature (at least not on 27.0.50).

I don't know why ti isn't doing what you expect, though...

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlqKuJQACgkQBcgs9XrR2kaWYACggHyx+NU6iCJ0cadfrO2d78TF
GW0An1xe9g9gfrd7L87WV8Lwmg/dm0hH
=UbYA
-----END PGP SIGNATURE-----