unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Van Ly <van.ly@sdf.org>, Juri Linkov <juri@linkov.net>
Cc: "57160@debbugs.gnu.org" <57160@debbugs.gnu.org>
Subject: bug#57160: 28.1.91; Info Virtual Index fails on search "two column"
Date: Fri, 12 Aug 2022 18:24:29 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488276554F3C98D091F072DF3679@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <7c71a8ae-3ce-a190-506d-155d40406443@SDF.ORG>

> Everyday search engines would accept "two column" and add in the hyphen.

(Not chiming in on whether something should be done in Info.)

Just pointing out that the "everyday search engines" you're thinking of (e.g. PDF searching, web search engines...) typically perform what's called "full-text search" or "indexed search".

They _index_ a set of documents, breaking down words into roots, endings, etc.  So they can match singular/plural and other forms of words that have the same root, and perform other kinds of search (boolean predicates, nearness tests, etc.).

They don't do the kind of searching that Emacs does, in general.  Emacs searching is typically plain-text, and it allows for the use of regexps, for example.

These are two very different search worlds.  Try searching for "two-column" with Google search and not getting hits also for "two column".  Each kind of search has its advantages.  Emacs searching is good for most uses of Emacs.





  reply	other threads:[~2022-08-12 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 17:11 bug#57160: 28.1.91; Info Virtual Index fails on search "two column" Van Ly
2022-08-12 17:42 ` Juri Linkov
2022-08-12 18:01   ` Van Ly
2022-08-12 18:24     ` Drew Adams [this message]
2022-08-14 12:48       ` Van Ly
2022-08-12 18:48     ` Eli Zaretskii
2022-08-12 19:28       ` Van Ly

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=SJ0PR10MB5488276554F3C98D091F072DF3679@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=57160@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=van.ly@sdf.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).