unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Artur Malabarba
	<bruce.connor.am-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: 21148-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
Subject: bug#21148: 25.0.50; Huge problems with case-insensitive search
Date: Tue, 28 Jul 2015 15:50:31 +0200	[thread overview]
Message-ID: <86lhe0fl20.fsf@example.com> (raw)
In-Reply-To: <mailman.7537.1438089852.904.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org> (Artur Malabarba's message of "Tue, 28 Jul 2015 14:23:35 +0100")

Artur Malabarba <bruce.connor.am-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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





  parent reply	other threads:[~2015-07-28 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  8:44 bug#21148: 25.0.50; Huge problems with case-insensitive search Sebastien Vauban
2015-07-28 13:23 ` Artur Malabarba
     [not found] ` <mailman.7537.1438089852.904.bug-gnu-emacs@gnu.org>
     [not found]   ` <mailman.7537.1438089852.904.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-07-28 13:50     ` Sebastien Vauban [this message]
2015-07-28 14:10       ` Artur Malabarba
2015-07-28 23:15         ` Artur Malabarba

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=86lhe0fl20.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=21148-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org \
    --cc=bruce.connor.am-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).