all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 27818@debbugs.gnu.org
Subject: bug#27818: 26.0.50; *occur* buffer misses one match
Date: Tue, 25 Jul 2017 11:21:00 +0200	[thread overview]
Message-ID: <mvmd18ox477.fsf@suse.de> (raw)
In-Reply-To: <CAH8Pv0jb=KrWovV6gm6URP2NLV4hJuTfQD6YPo3KGU5qjCEBaA@mail.gmail.com> (Dani Moncayo's message of "Tue, 25 Jul 2017 10:45:13 +0200")

On Jul 25 2017, Dani Moncayo <dmoncayo@gmail.com> wrote:

> Recipe from "emacs -Q":
>
> 1.  Create a new buffer and put there these four lines:
> ---begin-of-buffer---------
> w1    # word 1
> w2    # word 2
> w3    # word 3
> w4    # word 4
> ---end-of-buffer---------
>
> 2. Search for the following regexp:
> "[^[:alnum:]]\(w2\|w3\)[^[:alnum:]]" (without the quotes)
>
> 3.  End the search and type "C-M-s M-p RET M-s o" to launch an *occur* buffer.
>
> The search actually has 2 matches but the *occur* buffer shows only one of them:

The occur engine only considers non-overlapping matches and extends each
match to complete lines.

> ---begin-of-buffer---------
> 1 match for "[^[:alnum:]]\(w2\|w3\)[^[:alnum:]]" in buffer: foo
>       1:w1    # word 1
>        :w2    # word 2
> ---end-of-buffer---------

Note how the first [^[:alnum:]] matches the newline preceding w2, thus
the match includes also line 1.  The next match would start at the
newline in line 2, but that would overlap with the first match.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."





  reply	other threads:[~2017-07-25  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  8:45 bug#27818: 26.0.50; *occur* buffer misses one match Dani Moncayo
2017-07-25  9:21 ` Andreas Schwab [this message]
2017-07-25 10:23   ` Dani Moncayo
2017-07-25 10:57     ` Dani Moncayo
2017-07-29  8:26       ` 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=mvmd18ox477.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=27818@debbugs.gnu.org \
    --cc=dmoncayo@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.