all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: John Wiegley <jwiegley@gmail.com>
Cc: 28584@debbugs.gnu.org
Subject: bug#28584: 24.5; Emacs manual: add index entries for `multi-isearch-*' commands
Date: Mon, 25 Sep 2017 06:41:56 -0700 (PDT)	[thread overview]
Message-ID: <09b64866-de79-423d-b001-b00366d22500@default> (raw)
In-Reply-To: <m2wp4nmmeb.fsf@newartisans.com>

> > Not sure what you mean by "the second index entries". Both of the index
> > entries I mentioned go to the same place - doc about tags search (only).
> 
> I mean the second thing you had listed:
>     `search and replace in multiple files'
> But now I see that also refers to Tags-based search and replace.
> 
> Yes, we should have an index entry for Isearching across files.

And across (non-file) buffers.

And not just Isearching.  The same node includes `multi-occur*'.

And not just an _addition_ of index entries for this (for both
files and buffers).  The _existing_ index entries I mentioned
are misleading.  They should be changed to specify finding
certain "identifiers" in files (but not non-file buffers, I
imagine).  They are not really about searching, in the general
sense.

IOW, we should have index entries for (1) actually searching
and other index entries for (2) finding identifiers.  (The
former can find text matches of any kind, not just identifiers.)





  reply	other threads:[~2017-09-25 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 17:49 bug#28584: 24.5; Emacs manual: add index entries for `multi-isearch-*' commands Drew Adams
2017-09-24 23:09 ` John Wiegley
2017-09-25  0:38   ` Drew Adams
2017-09-25  4:29     ` John Wiegley
2017-09-25 13:41       ` Drew Adams [this message]
2017-09-25 14:16         ` John Wiegley
2017-09-25 15:13           ` Drew Adams
2017-09-25 15:20             ` John Wiegley
2017-09-30 12:11     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09b64866-de79-423d-b001-b00366d22500@default \
    --to=drew.adams@oracle.com \
    --cc=28584@debbugs.gnu.org \
    --cc=jwiegley@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 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.