unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to grep for a string spanning multiple lines?
Date: Sun, 27 Nov 2022 14:48:52 +0100	[thread overview]
Message-ID: <87edtoh5iz.fsf@dataswamp.org> (raw)
In-Reply-To: 871qpodgzn.fsf@mbork.pl

Marcin Borkowski wrote:

>>> I remember that someone in some video said something, and
>>> I want to find that part. However, it turns out that it is
>>> split between two (or more) lines.
>>
>> (re-search-forward ";; Hello my friend\n;; stay a while, and listen")
>>
>> ;; Hello my friend
>> ;; stay a while, and listen
>
> Well, that's obviously cheating. The real problem is how to
> search when you have no idea where you have spaces and where
> you have newlines...

Okay, I didn't understand ... you want to search for something
you or someone else said (wrote), but you only remember the
words, not punctuation, whitespace etc?

It can be done with regular expressions of course, but ...
I wonder if it isn't better to have some "inexact" search
algorithm which quantifies the proximity or score of each
inexact hit in a set of results, so that - if I just make
things up for a possible search for "Hello my friend" in
a body of text where it doesn't quite exist - it could produce
fallout such as

  results           score
  -----------------------
  Hello my Fräulein   89%
  Hello MySQL         28%
  Go to Helvetia       3%

Because the advantage would then also be that even the words
wouldn't have to be exact!

Interesting, I'd like that myself very much!

Do we have that?

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2022-11-27 13:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26  6:42 How to grep for a string spanning multiple lines? Marcin Borkowski
2022-11-26  8:27 ` Jean Louis
2022-11-26  8:36 ` tomas
2022-11-26  8:43   ` Jean Louis
2022-11-26  8:59     ` Eli Zaretskii
2022-11-26  9:06       ` Jean Louis
2022-11-27  7:31         ` Michael Heerdegen
2022-11-27  7:44           ` Jean Louis
2022-11-27 12:04             ` Michael Heerdegen
2022-11-27 18:25               ` Jean Louis
2022-11-26 10:57 ` Arthur Miller
2022-11-26 14:55 ` Emanuel Berg
2022-11-27  6:54   ` Marcin Borkowski
2022-11-27  7:26     ` Jean Louis
2022-11-27 13:48     ` Emanuel Berg [this message]
2022-11-27 18:10       ` tomas
2022-11-27 19:04         ` Emanuel Berg
2022-11-27 19:46         ` [External] : " Drew Adams
2022-11-28  5:07           ` tomas
2022-11-28  6:17             ` Drew Adams
2022-11-29  2:00               ` Emanuel Berg
2022-11-28 21:05             ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-28 21:12               ` Emanuel Berg
2022-11-28 21:17               ` Emanuel Berg
2022-12-04 21:55 ` Rudolf Adamkovič
2022-12-05 23:06   ` Emanuel Berg

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=87edtoh5iz.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=help-gnu-emacs@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.
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).