From: Mauro Aranda <maurooaranda@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
2807@debbugs.gnu.org, 44494@debbugs.gnu.org
Cc: pot@gnu.org, MON KEY <monkey@sandpframing.com>,
prouleau001@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>,
Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Subject: bug#44494: bug#2807: Subject: 23.0.90; etags can't access .el.gz files
Date: Thu, 12 Oct 2023 09:51:09 -0300 [thread overview]
Message-ID: <1d2774ad-831d-4c63-9e5a-42b07d47ddce@gmail.com> (raw)
In-Reply-To: <5a81da67-32a8-4b94-99e5-5c023f27ca30@yandex.ru>
On 12/10/23 09:44, Dmitry Gutov wrote:
> On 12/10/2023 15:39, Mauro Aranda wrote:
>> For reproducing Bug#44494, I follow the same steps, but instead of
>> executing tags-search I do:
>> (require 'xref)
>> M-x xref-etags-mode
>> C-u M-. tags-search
>
> tags-search is not an Xref command. So whether you load 'xref' and
turn on xref-etags-mode, or not, should have no effect on how
'tags-search' works.
I'm not running tags-search in recipe for Bug#44494. I'm asking
xref-find-definitions (M-.) to find the definition of tags-search.
next prev parent reply other threads:[~2023-10-12 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 3:39 bug#2807: Subject: 23.0.90; etags can't access .el.gz files MON KEY
2011-09-11 22:14 ` Lars Magne Ingebrigtsen
2011-09-13 11:51 ` Francesco Potortì
2011-09-13 18:09 ` Stefan Monnier
2011-10-06 22:05 ` Lars Magne Ingebrigtsen
2011-10-07 1:52 ` Stefan Monnier
2011-10-07 10:25 ` Lars Magne Ingebrigtsen
2011-10-07 13:29 ` Stefan Monnier
2011-10-07 14:38 ` Lars Magne Ingebrigtsen
2011-09-13 18:24 ` Lars Magne Ingebrigtsen
2023-10-12 12:39 ` Mauro Aranda
2023-10-12 12:44 ` bug#44494: " Dmitry Gutov
2023-10-12 12:51 ` Mauro Aranda [this message]
2023-10-12 15:47 ` Dmitry Gutov
2023-10-12 12:46 ` bug#44494: " Mauro Aranda
2023-10-12 14:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 15:04 ` Mauro Aranda
2023-10-15 4:12 ` Stefan Monnier 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=1d2774ad-831d-4c63-9e5a-42b07d47ddce@gmail.com \
--to=maurooaranda@gmail.com \
--cc=2807@debbugs.gnu.org \
--cc=44494@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monkey@sandpframing.com \
--cc=monnier@iro.umontreal.ca \
--cc=pot@gnu.org \
--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).