unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Rouleau <prouleau001@gmail.com>
Cc: 44494@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#44494: etags.el xref-location-marker does not handle TAGS references to .el.gz files
Date: Sat, 07 Nov 2020 16:22:48 +0200	[thread overview]
Message-ID: <83a6vt6ybr.fsf@gnu.org> (raw)
In-Reply-To: <CALTqLiZuDKW3QJhfqEaK=J4aqJ_qAh-TTpB19sf0jg=d+w=bwA@mail.gmail.com> (message from Pierre Rouleau on Sat, 7 Nov 2020 09:15:12 -0500)

> From: Pierre Rouleau <prouleau001@gmail.com>
> Date: Sat, 7 Nov 2020 09:15:12 -0500
> Cc: dgutov@yandex.ru, 44494@debbugs.gnu.org
> 
> With both emacs 26.3 and 27.1, iI do:
> . emacs -Q
> . C-x C-f lisp/simple.el
> . C-u M-x cc-require
> ==> message: No definitions found for cc-require
> 
> At this point:
> - the xref backend is the default for .el files; etags.
> - xref-backend-functions is set to (elisp--xref-backend t), a local setting.
> - the abbrev feature is loaded, as M-: (featurep 'abbrev) returns t.
> - So looking for kill-all-abbrevs using the elisp--xref-backend works, my 
>   understanding is that it works because the file that holds the definition 
>   is loaded.

How does this explain the fact that find-tag also worked for me?  Does
it work for you?





  reply	other threads:[~2020-11-07 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 23:22 bug#44494: etags.el xref-location-marker does not handle TAGS references to .el.gz files Pierre Rouleau
2020-11-07  2:22 ` Dmitry Gutov
2020-11-07  3:31   ` Pierre Rouleau
2020-11-07  8:00     ` Eli Zaretskii
2020-11-07 14:15       ` Pierre Rouleau
2020-11-07 14:22         ` Eli Zaretskii [this message]
2020-11-07 14:37         ` Eli Zaretskii
2020-11-07 14:48           ` Pierre Rouleau
2020-11-07 15:39             ` Pierre Rouleau
2020-11-07 15:52               ` Eli Zaretskii
2020-11-07 16:09                 ` Pierre Rouleau
2020-11-07  7:18 ` Eli Zaretskii

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=83a6vt6ybr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44494@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=prouleau001@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).