From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: 6716@debbugs.gnu.org
Subject: bug#6716: 23.2; Setting `find-function-source-path' has no effect.
Date: Sun, 13 Feb 2022 11:02:33 +0100 [thread overview]
Message-ID: <877d9zw0cm.fsf@gnus.org> (raw)
In-Reply-To: <874ofpqeiu.fsf@gmail.com> ("Štěpán Němec"'s message of "Sat, 24 Jul 2010 13:56:41 +0200")
Štěpán Němec <stepnem@gmail.com> writes:
> Because `find-library-name' receives as its LIBRARY argument the full
> path, but doesn't strip the directory part, setting
> `find-function-source-path' has no effect on symbol finding -- Emacs
> still tries the path guessed according to load path (which is not
> correct in case you have the Elisp sources in directory different from
> the compiled files).
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
`find-function-source-path' is now obsolete (`find-library-source-path'
is used instead), but there wasn't a case to reproduce the problem here.
Are there still problems in this area in recent Emacs versions? If so,
do you have a recipe to reproduce the problem?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-02-13 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 11:56 bug#6716: 23.2; Setting `find-function-source-path' has no effect Štěpán Němec
2010-07-25 23:45 ` Stefan Monnier
2010-07-26 4:17 ` Štěpán Němec
2010-07-26 4:51 ` Štěpán Němec
2010-07-26 10:23 ` Stefan Monnier
2010-07-26 11:20 ` Štěpán Němec
2010-07-26 21:44 ` Stefan Monnier
2010-07-27 10:07 ` Štěpán Němec
2010-07-27 11:57 ` Stefan Monnier
2010-07-26 21:40 ` MON KEY
2010-07-27 9:39 ` Štěpán Němec
2010-07-28 1:38 ` MON KEY
2022-02-13 10:02 ` Lars Ingebrigtsen [this message]
2022-02-15 14:50 ` Štěpán Němec
2022-02-17 11:33 ` Lars Ingebrigtsen
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=877d9zw0cm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=6716@debbugs.gnu.org \
--cc=stepnem@gmail.com \
/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.