From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: lax matching is not a great default behavior Date: Wed, 02 Dec 2015 05:37:39 +0200 Message-ID: <83lh9djzb0.fsf@gnu.org> 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> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1449027482 19994 80.91.229.3 (2 Dec 2015 03:38:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Dec 2015 03:38:02 +0000 (UTC) Cc: mvoteiza@udel.edu, emacs-devel@gnu.org To: bruce.connor.am@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 02 04:37: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 1a3yEq-0004N4-7N for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 04:37:52 +0100 Original-Received: from localhost ([::1]:55971 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3yEp-0007OL-5x for ged-emacs-devel@m.gmane.org; Tue, 01 Dec 2015 22:37:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33896) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3yEl-0007O4-FA for emacs-devel@gnu.org; Tue, 01 Dec 2015 22:37:48 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a3yEg-0005mk-F1 for emacs-devel@gnu.org; Tue, 01 Dec 2015 22:37:47 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:53056) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3yEg-0005mf-79 for emacs-devel@gnu.org; Tue, 01 Dec 2015 22:37:42 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NYP00F00OFMRE00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Wed, 02 Dec 2015 05:37:40 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NYP00F5NOQSRG10@a-mtaout22.012.net.il>; Wed, 02 Dec 2015 05:37:40 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 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:195730 Archived-At: > 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?