From: Juri Linkov <juri@jurta.org>
To: emacs-devel@gnu.org
Subject: Occur in Word Isearch
Date: Sun, 09 Nov 2008 23:09:03 +0200 [thread overview]
Message-ID: <87skq0mwuk.fsf_-_@jurta.org> (raw)
In-Reply-To: <87d4h5ew7x.fsf@jurta.org> (Juri Linkov's message of "Sat, 08 Nov 2008 23:57:34 +0200")
`M-s w word M-s o' displays a *Occur* buffer with wrong matches because
it takes no care about word boundaries. The following patch should fix this.
Index: lisp/isearch.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/isearch.el,v
retrieving revision 1.331
diff -c -r1.331 isearch.el
*** lisp/isearch.el 19 Oct 2008 22:33:17 -0000 1.331
--- lisp/isearch.el 9 Nov 2008 21:07:54 -0000
***************
*** 1384,1390 ****
string. NLINES has the same meaning as in `occur'."
(interactive
(list
! (if isearch-regexp isearch-string (regexp-quote isearch-string))
(if current-prefix-arg (prefix-numeric-value current-prefix-arg))))
(let ((case-fold-search isearch-case-fold-search)
;; set `search-upper-case' to nil to not call
--- 1390,1399 ----
string. NLINES has the same meaning as in `occur'."
(interactive
(list
! (cond
! (isearch-word (concat "\\b" (regexp-quote isearch-string) "\\b"))
! (isearch-regexp isearch-string)
! (t (regexp-quote isearch-string)))
(if current-prefix-arg (prefix-numeric-value current-prefix-arg))))
(let ((case-fold-search isearch-case-fold-search)
;; set `search-upper-case' to nil to not call
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-11-09 21:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 9:56 Isearch in dired Richard M. Stallman
2008-11-08 10:59 ` Juri Linkov
2008-11-08 11:33 ` Lennart Borgman
2008-11-08 12:23 ` Alan Mackenzie
2008-11-08 15:22 ` Lennart Borgman
2008-11-08 17:07 ` Juri Linkov
2008-11-09 0:26 ` Richard M. Stallman
2008-11-09 21:57 ` Juri Linkov
2008-11-08 12:19 ` Alan Mackenzie
2008-11-08 17:08 ` Juri Linkov
2008-11-08 14:10 ` Chong Yidong
2008-11-08 16:05 ` joakim
2008-11-08 17:27 ` Juri Linkov
2008-11-08 17:17 ` Juri Linkov
2008-11-09 0:26 ` Richard M. Stallman
2008-11-08 21:57 ` Lazy " Juri Linkov
2008-11-09 20:54 ` recursive-edit in Isearch Juri Linkov
2008-11-09 21:09 ` Juri Linkov [this message]
2008-11-13 15:29 ` Occur in Word Isearch Chong Yidong
2008-11-13 15:30 ` Lazy Isearch in dired Chong Yidong
2008-11-13 15:32 ` Chong Yidong
2008-11-13 16:30 ` Juri Linkov
2008-11-13 17:07 ` Chong Yidong
2008-11-09 14:22 ` Chong Yidong
2008-11-09 15:08 ` Stefan Monnier
2008-11-09 17:59 ` Juri Linkov
2008-11-11 22:55 ` Chong Yidong
2008-11-12 2:59 ` Stefan Monnier
2008-11-12 11:59 ` René Kyllingstad
2008-11-12 15:13 ` Drew Adams
2008-11-12 15:53 ` Richard M. Stallman
2008-11-12 7:55 ` Juri Linkov
2008-11-12 15:08 ` Chong Yidong
2008-11-13 16:57 ` Juri Linkov
2008-11-16 22:22 ` Juri Linkov
2008-11-10 3:11 ` Richard M. Stallman
2008-11-11 21:35 ` Juri Linkov
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=87skq0mwuk.fsf_-_@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@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.
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).