From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 f8208b6: Document the user-level features of the Xref package
Date: Thu, 21 Jan 2016 06:28:51 +0300 [thread overview]
Message-ID: <56A05073.5090100@yandex.ru> (raw)
In-Reply-To: <8337tsc133.fsf@gnu.org>
On 01/20/2016 07:43 AM, Eli Zaretskii wrote:
> "Xref" is the name of the node, not of the section. And the node's
> name does not mean it describes xref the package; this is user-level
> documentation. If you have a better suggestion for a short name of a
> node which aims at describing features most of which have "xref-" in
> their names, please tell.
Cross-Referencing? A native speaker might have a better suggestion.
> AFAICT, your additions are not directly related to this section; they
> are not mentioned in it.
Hmm. When I asked what we needed to obsolete tags-loop-continue, you
only mentioned Dired commands.
http://lists.gnu.org/archive/html/emacs-devel/2016-01/msg00842.html
> No, dired-do-find-regexp cannot replace it, because it looks through
> all the files in the directory, whereas tags-search looks in the files
> recorded in the tags tables.
Ok, dired-do-find-regexp cannot. What about project-or-external-find-regexp?
By default, when the VC project backend is used, and
project-vc-external-roots-function is at its default value,
project-or-external-find-regexp will search the current project, as well
as the directories of the tags tables, if they are outside of it.
Or, in emacs-lisp-mode, it will search the load-path directories.
> We should have an xref-based replacement
> for tags-search and tags-query-replace, which would similarly search
> through the "relevant" files.
tags-query-replace? We have xref-query-replace already, and it's more
flexible: depending on which results it's called from, it'll perform
replacements in simple regexp matches, or in "smarter" list of
references (or other similar kinds of results).
Back to tags-search.
Like described above, we have a command that goes further that it
already. So what would be the goal of having xref-find-regexp? Just to
tick off a box and simplify updating the manual?
It will require adding a new method to xref backends, with clear
semantics and purpose. Backend authors will want to know why they
implement it, and why a user might want to use xref-find-regexp, instead
of the aforementioned alternative.
Suppose we're in emacs-lisp-mode. What will xref-find-regexp do? Will it
search the load-path elements, but skip the current project, however
it's defined, if it's not in load-path? Will it only search *.el files
inside load-path directories, and ignore files with all other extensions?
> (Btw, I think replacing tags-search and tags-query-replace with
> commands that start with "project-" is not a good idea, for the same
I definitely never suggested replacing tags-query-replace with project-
anything. The new "replace" workflow is two-step: two the search (using
some command that creates an xref buffer), then call xref-query-replace.
next prev parent reply other threads:[~2016-01-21 3:28 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160109191428.26341.44105@vcs.savannah.gnu.org>
[not found] ` <E1aHyy4-0006rU-Td@vcs.savannah.gnu.org>
2016-01-10 3:02 ` [Emacs-diffs] emacs-25 f8208b6: Document the user-level features of the Xref package Dmitry Gutov
2016-01-10 15:50 ` Eli Zaretskii
2016-01-10 18:05 ` Dmitry Gutov
2016-01-10 18:59 ` Eli Zaretskii
2016-01-10 19:32 ` Dmitry Gutov
2016-01-10 20:51 ` Eli Zaretskii
2016-01-10 21:11 ` Dmitry Gutov
2016-01-11 3:33 ` Eli Zaretskii
2016-01-11 16:55 ` Dmitry Gutov
2016-01-11 17:52 ` Eli Zaretskii
2016-01-11 19:09 ` Dmitry Gutov
2016-01-11 19:31 ` Eli Zaretskii
2016-01-11 19:41 ` Dmitry Gutov
2016-01-11 20:14 ` Eli Zaretskii
2016-01-11 20:21 ` Dmitry Gutov
2016-01-18 17:31 ` Eli Zaretskii
2016-01-18 22:18 ` Dmitry Gutov
2016-01-19 17:41 ` Eli Zaretskii
2016-01-19 21:53 ` Dmitry Gutov
2016-01-20 4:43 ` Eli Zaretskii
2016-01-20 7:28 ` John Wiegley
2016-01-20 20:53 ` Dmitry Gutov
2016-01-20 21:03 ` John Wiegley
2016-01-20 21:09 ` Dmitry Gutov
2016-01-21 19:01 ` Stephen Leake
2016-01-21 20:32 ` Dmitry Gutov
2016-01-21 3:46 ` Eli Zaretskii
2016-01-21 3:28 ` Dmitry Gutov [this message]
2016-01-21 17:29 ` Eli Zaretskii
2016-01-21 18:46 ` Dmitry Gutov
2016-01-21 19:00 ` Eli Zaretskii
2016-01-21 19:46 ` Dmitry Gutov
2016-01-21 20:02 ` Eli Zaretskii
2016-01-21 20:10 ` Dmitry Gutov
2016-01-21 20:32 ` Eli Zaretskii
2016-01-21 21:40 ` Dmitry Gutov
2016-01-24 2:20 ` Dmitry Gutov
2016-01-24 15:29 ` Eli Zaretskii
2016-01-25 20:38 ` Ken Brown
2016-01-25 20:52 ` Eli Zaretskii
2016-01-25 21:29 ` Dmitry Gutov
2016-01-26 2:44 ` Ken Brown
2016-01-26 6:22 ` Dmitry Gutov
2016-01-21 19:19 ` Stephen Leake
2016-01-21 19:26 ` Dmitry Gutov
2016-01-22 7:40 ` Stephen Leake
2016-01-22 8:21 ` Eli Zaretskii
2016-01-22 10:46 ` Dmitry Gutov
2016-01-22 13:37 ` Eli Zaretskii
2016-01-22 10:07 ` Dmitry Gutov
2016-01-21 20:09 ` Eli Zaretskii
2016-01-22 18:16 ` John Yates
2016-01-19 5:36 ` John Wiegley
2016-01-19 5:47 ` Dmitry Gutov
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=56A05073.5090100@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 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.