GNU bug report logs -
#21148
25.0.50; Huge problems with case-insensitive search
Previous Next
Reported by: Sebastien Vauban <sva-news <at> mygooglest.com>
Date: Tue, 28 Jul 2015 08:45:02 UTC
Severity: normal
Tags: moreinfo, notabug
Merged with 21149
Found in version 25.0.50
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21148 in the body.
You can then email your comments to 21148 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#21148
; Package
emacs
.
(Tue, 28 Jul 2015 08:45:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Sebastien Vauban <sva-news <at> mygooglest.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 28 Jul 2015 08:45:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
As you can see on the screencast http://screencast.com/t/nq7xkfJiy,
case-insensitive [1] searches are becoming very fuzzy to me.
Sample text file:
--8<---------------cut here---------------start------------->8---
Let's search for all case-insensitive occurrences of "workingd"...
#+begin_src shell :var workingDir=(file-name-directory (buffer-file-name))
# No init file.
cmd="$EMACS -q -l ${workingDir}.init.el"
#+end_src
--8<---------------cut here---------------end--------------->8---
Recipe:
- Incremantally search (with `C-s') for "workingd"
Problems:
- While point is at the beginning of the buffer, and while the string
"workingd" exists in the buffer, Isearch tells me from the start that
it fails finding my pattern!??
- As the search is case-insensitive, `C-s' should allow me to cycle
between the 3 strings found (1 "workingd" and 2 "workingD"), but it
finally only finds the exact match "workingd".
Note -- Anzu correctly reports me (in the modeline) that there are
3 found strings...
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2015-07-03 on LEG570
Repository revision: 2b848fadd51e805b2f46da64c5958ea7f009048a
Windowing system distributor `Microsoft Corp.', version 6.3.9600
Configured using:
`configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'
Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
TOOLKIT_SCROLL_BARS
[1] ┌────
│ case-fold-search is a variable defined in ‘C source code’.
│ Its value is t
│
│ Automatically becomes buffer-local when set.
│
│ Documentation:
│ Non-nil if searches and matches should ignore case.
└────
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#21148
; Package
emacs
.
(Tue, 28 Jul 2015 13:24:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 21148 <at> debbugs.gnu.org (full text, mbox):
What value do you have for `isearch-search-fun-function'?
Also, could you see if all ofthese problems still happen when you
don't use anzu? (just to help narrow things down).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#21148
; Package
emacs
.
(Tue, 28 Jul 2015 13:51:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 21148 <at> debbugs.gnu.org (full text, mbox):
Artur Malabarba <bruce.connor.am <at> gmail.com> writes:
> What value do you have for `isearch-search-fun-function'?
┌────
│ isearch-search-fun-function is a variable defined in ‘isearch.el’.
│ Its value is fuzzy-isearch
└────
> Also, could you see if all ofthese problems still happen when you
> don't use anzu? (just to help narrow things down).
I guess I'd better should try without using `fuzzy', then?
--8<---------------cut here---------------start------------->8---
;; fuzzy matching (must-have!)
(with-eval-after-load "fuzzy-autoloads"
(autoload 'turn-on-fuzzy-isearch "fuzzy" nil t)
(add-hook 'isearch-mode-hook #'turn-on-fuzzy-isearch))
--8<---------------cut here---------------end--------------->8---
Indeed, removing that resolve this problem...
Though, fuzzy was quite useful. Is there a standard Emacs alternative to
it?
Best regards,
Seb
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#21148
; Package
emacs
.
(Tue, 28 Jul 2015 14:11:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 21148 <at> debbugs.gnu.org (full text, mbox):
> --8<---------------cut here---------------start------------->8---
> ;; fuzzy matching (must-have!)
> (with-eval-after-load "fuzzy-autoloads"
> (autoload 'turn-on-fuzzy-isearch "fuzzy" nil t)
> (add-hook 'isearch-mode-hook #'turn-on-fuzzy-isearch))
> --8<---------------cut here---------------end--------------->8---
>
> Indeed, removing that resolve this problem...
>
> Though, fuzzy was quite useful. Is there a standard Emacs alternative to
> it?
Report an issue to fuzzy, I'm sure it's easy to solve. I had a very
similar problem with longlines-mode, and it was a very simple fix.
CC me in the issue report (If it's on Github ping me @Malabarba) and
I'll help sort it out.
Added tag(s) notabug.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Tue, 28 Jul 2015 15:49:02 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
21148 <at> debbugs.gnu.org and Sebastien Vauban <sva-news <at> mygooglest.com>
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Tue, 28 Jul 2015 15:49:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#21148
; Package
emacs
.
(Tue, 28 Jul 2015 23:16:02 GMT)
Full text and
rfc822 format available.
Message #21 received at 21148-done <at> debbugs.gnu.org (full text, mbox):
Marking this as fixed, it has been reported to fuzzy-el:
https://github.com/auto-complete/fuzzy-el/issues/8
For future, the problem here is that there are some search packages
which set the `isearch-search-fun-function' to their own
(poorly-written) function. In this case (and on longlines-mode) the
issue is that the function does the following check:
(cond (isearch-word
(if isearch-forward 'word-search-forward 'word-search-backward))
...)
This assumes that `isearch-word' only ever has a boolean meaning, but
it's been a while now that this variable can also hold a function.
That's how symbol-isearch is implemented, in fact.
The reason these problems weren't reported before, is that the default
value of isearch-word was still nil up until now, but enabling
char-fold by default changed the default value to a function.
Forcibly Merged 21148 21149.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Wed, 29 Jul 2015 15:32:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 27 Aug 2015 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 9 years and 358 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.