From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: Re: Matches for multiline regexps
Date: Wed, 15 Jun 2005 21:09:04 -0500 (CDT) [thread overview]
Message-ID: <200506160209.j5G294126098@raven.dms.auburn.edu> (raw)
In-Reply-To: <200506160140.j5G1eFJ26066@raven.dms.auburn.edu> (message from Luc Teirlinck on Wed, 15 Jun 2005 20:40:15 -0500 (CDT))
Or does occur have problems with multiline regexps?
In my previous example buffer:
11
11
11
11
11
`M-x occur RET 11 C-q C-j 11 RET' produces the following *Occur*
buffer:
4 matches for "11
11" in buffer: bu
2:11
4:11
6:11
8:11
I could not find out from the docs what those numbers in front of the
11's are supposed to mean. They are clearly not line numbers.
Starting from a buffer with the following five lines:
11
22
33
11
22
`M-x occur RET 11 C-q C-j 22 RET' produces the following *Occur*
buffer:
2 matches for "11
22" in buffer: bu
2:11
6:11
This at the very least seems inconsistent with the `occur' docstring:
Show all lines in the current buffer containing a match for regexp.
If a match spreads across multiple lines, all those lines are shown.
So why do I not see any 22 lines in the *Occur* buffer?
Sincerely,
Luc.
next prev parent reply other threads:[~2005-06-16 2:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 1:40 Matches for multiline regexps Luc Teirlinck
2005-06-16 2:09 ` Luc Teirlinck [this message]
2005-06-16 2:24 ` Luc Teirlinck
2005-06-16 16:24 ` Richard Stallman
2005-06-17 3:26 ` Luc Teirlinck
2005-06-17 14:58 ` Richard Stallman
2005-06-18 2:48 ` Luc Teirlinck
2005-06-19 3:50 ` Richard Stallman
2005-06-19 14:14 ` Juri Linkov
2005-06-20 3:50 ` Richard Stallman
2005-06-20 4:47 ` Juri Linkov
2005-06-21 2:00 ` Richard Stallman
2005-06-20 1:57 ` Luc Teirlinck
2005-06-20 17:51 ` Richard Stallman
2005-06-18 3:17 ` Luc Teirlinck
2005-06-17 3:30 ` Luc Teirlinck
2005-06-17 14:58 ` Richard Stallman
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=200506160209.j5G294126098@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
/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.