unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [Emacs-diffs] emacs-25 035bd81: Update documentation for Dired search and replace
Date: Sat, 23 Jan 2016 10:10:12 +0300	[thread overview]
Message-ID: <56A32754.4010102@yandex.ru> (raw)
In-Reply-To: <E1aMs4r-0004lR-Mj@vcs.savannah.gnu.org>

On 01/23/2016 09:53 AM, Eli Zaretskii wrote:
> branch: emacs-25
> commit 035bd8159fe5bcea15eacc8a23ab54f4bc3b6f17
> Author: Eli Zaretskii <eliz@gnu.org>
> Commit: Eli Zaretskii <eliz@gnu.org>
>
>      Update documentation for Dired search and replace
>
>      * doc/emacs/dired.texi (Operating on Files): Update descriptions
>      of 'A' and 'Q' now bound to 'dired-do-find-regexp' and
>      'dired-do-find-regexp-and-replace'.
>
>      * etc/NEWS: Mention xref-related changes in Dired.

Looks good overall, thanks.

> +(@code{dired-do-find-regexp}).

> +This command is a variant of @code{xref-find-apropos}
> +(@pxref{Identifier Search}), it displays the @file{*xref*} buffer,
> +where you can navigate between matches and display them as needed
> +using the commands described in @ref{Xref Commands}.

That's rather wrong: dired-do-find-regexp performs regexp-search inside 
the files.

xref-find-apropos, on the other hand, performs regexp search inside the 
definitions index (obarray for elisp backend, and TAGS file for etags 
backend).

Although I get that you might want to avoid mentioning 
project-find-regexp here, and there's no other suitable command to 
compare to.



       reply	other threads:[~2016-01-23  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160123065341.18279.32482@vcs.savannah.gnu.org>
     [not found] ` <E1aMs4r-0004lR-Mj@vcs.savannah.gnu.org>
2016-01-23  7:10   ` Dmitry Gutov [this message]
2016-01-23  8:07     ` [Emacs-diffs] emacs-25 035bd81: Update documentation for Dired search and replace Eli Zaretskii
2016-01-23  8:10       ` Dmitry Gutov
2016-01-23 11:47         ` 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=56A32754.4010102@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 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).