From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: 42940@debbugs.gnu.org
Subject: bug#42940: feature/native-comp; xref-find-definition searches compile location of el files instead of install location
Date: Thu, 20 Aug 2020 11:05:00 +0000 [thread overview]
Message-ID: <xjfwo1t60ir.fsf@sdf.org> (raw)
In-Reply-To: <CA+G3_PPQ97y8uzafvEZt_SdS6zxTu-RStqg0owu0tkOEA+w-Tw@mail.gmail.com> (Tom Gillespie's message of "Wed, 19 Aug 2020 15:22:22 -0700")
Tom Gillespie <tgbugs@gmail.com> writes:
> 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
Hi Tom,
I believe could be an issue related to commit I've just reverted, could
you give a try to the last state?
If you still see it could you open a bug in the emacs bug tracker about
that? I've a number of things in the queue and that's the best place to
cumulate and discuss these.
Thanks!
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-08-20 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 22:22 bug#42940: feature/native-comp; xref-find-definition searches compile location of el files instead of install location Tom Gillespie
2020-08-20 11:05 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=xjfwo1t60ir.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=42940@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=tgbugs@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 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).