From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: lax matching is not a great default behavior Date: Wed, 2 Dec 2015 13:06:22 +0000 Message-ID: References: <837fl2qzs2.fsf@gnu.org> <83610ikvto.fsf@gnu.org> <87vb8iqa0l.fsf@udel.edu> <87k2oyymjv.fsf@udel.edu> <83r3j6j5vj.fsf@gnu.org> <83poyqj5qb.fsf@gnu.org> <83lh9djzb0.fsf@gnu.org> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1449061614 30874 80.91.229.3 (2 Dec 2015 13:06:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Dec 2015 13:06:54 +0000 (UTC) Cc: Mark Oteiza , emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 02 14:06:53 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a477Q-0000sB-LR for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 14:06:48 +0100 Original-Received: from localhost ([::1]:58016 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a477P-0006Yh-UF for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 08:06:47 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58657) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a4779-0006XY-Fn for emacs-devel@gnu.org; Wed, 02 Dec 2015 08:06:35 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a4775-000727-19 for emacs-devel@gnu.org; Wed, 02 Dec 2015 08:06:31 -0500 Original-Received: from mail-lf0-x234.google.com ([2a00:1450:4010:c07::234]:35902) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a4773-00070f-Eq; Wed, 02 Dec 2015 08:06:25 -0500 Original-Received: by lfs39 with SMTP id 39so47018514lfs.3; Wed, 02 Dec 2015 05:06:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1NeyrDFjrYlc5oS61q8CjGgUULFaKJEtqA/QSq8Z9Q4=; b=qN7NzHzVfs7kpZVLkE041yBpSJSc1RmX65pqML84ZwC1KRmImDgQLJW2xfhTPoXzUP 5liXmSzKgrrWy8m6hKToZUiT+hIDTTc0MTEa2yrlLsmEX9QiKJ+ZbWzprmKiGROyWJ48 3qin4PVS4jY7KV3mycHcd8zW+SJZIYLTDL/r/pb8/H4k5dvw920W17G2g5Ib9tTACmYh 6QDp6t4KD3b5fWlkJ6b1wFNZXtP5xI9eAU7xQchWxrJprps2FiHIMc2MjL9XUQevXpsi CFLu5tTEMEjOwLlD5AptR9WAK8DOhjtoqnx/TMd6V9e5EPwk+IgPjiyG0lffTwCBZxu8 jlkQ== X-Received: by 10.25.147.84 with SMTP id v81mr2743884lfd.119.1449061583087; Wed, 02 Dec 2015 05:06:23 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Wed, 2 Dec 2015 05:06:22 -0800 (PST) In-Reply-To: <83lh9djzb0.fsf@gnu.org> X-Google-Sender-Auth: -Xarivzn2K7ruveZtuUbtUIkvh4 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c07::234 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:195741 Archived-At: 2015-12-02 3:37 GMT+00:00 Eli Zaretskii : >> Date: Tue, 1 Dec 2015 23:31:18 +0000 >> From: Artur Malabarba >> Cc: Mark Oteiza , emacs-devel >> >> > Seems to be lazy-highlight. Set isearch-lazy-highlight to nil, and >> > Bob's your uncle. >> >> If lazy-highlighting adds a lag before the user can move to the second >> match, then we need to fix lazy-highlighting to not block input. > > Yes, but do you understand why it's a problem anyway? Lazy hilighting > uses the same regexp search functions and the same regexp as the code > that find the first hit. We are talking about 2 cases where there's > no other matches for that regexp. So how come finding out that there > are no more matches is almost instantaneous, but looking for them as > part of lazy-highlighting is so slow? Yes. lazy-highlight is definitely doing something wrong. If I can hit C-s and instantly be told "no more matches", lazy-highlight shouldn't be slow at all. I just tested here and the same happens for me.