From: Tom Gillespie <tgbugs@gmail.com>
To: 42940@debbugs.gnu.org, akrl@sdf.org
Subject: bug#42940: feature/native-comp; xref-find-definition searches compile location of el files instead of install location
Date: Wed, 19 Aug 2020 15:22:22 -0700 [thread overview]
Message-ID: <CA+G3_PPQ97y8uzafvEZt_SdS6zxTu-RStqg0owu0tkOEA+w-Tw@mail.gmail.com> (raw)
Hi Andrea,
On feature/native-comp at 8a931a97b8dd19a38d6f719f810280a07ba76438
I am unable to use xref-find-definition to resolve a large subset of functions
including shell-command. This was not an issue at
9f01ce6327af886f26399924a9aadf16cdd4fd9f and is not an issue on master at
a566e409d0d962d3c2870691175836da22c31111. Repro is below and the messages
point to the cause being that xref-find-definitions is now looking in
the location where
the el files were during compilation instead of where they have been
installed. This
will cause problems for anyone distributing emacs in addition to distros where
compilation is sandboxed. To reproduce it on your end I suspect that
you will need
to use a different compile and install location for the el files. Best!
Tom
Repro:
emacs -q -batch --no-site-file --eval "(xref-find-definitions 'shell-command)"
Stdout:
No library /var/tmp/portage/app-editors/emacs-28.0.9999-r1/work/emacs/lisp/simple.el
in search path
No definitions found for: shell-command
next reply other threads:[~2020-08-19 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 22:22 Tom Gillespie [this message]
2020-08-20 11:05 ` bug#42940: feature/native-comp; xref-find-definition searches compile location of el files instead of install location Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-20 11:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-20 21:36 ` Tom Gillespie
2020-08-21 7:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-22 21:53 ` Tom Gillespie
2020-08-22 23:46 ` Tom Gillespie
2020-08-29 18:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-30 3:09 ` Tom Gillespie
2020-08-30 7:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=CA+G3_PPQ97y8uzafvEZt_SdS6zxTu-RStqg0owu0tkOEA+w-Tw@mail.gmail.com \
--to=tgbugs@gmail.com \
--cc=42940@debbugs.gnu.org \
--cc=akrl@sdf.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).