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 15:45:31 +0200 Message-ID: <83h9k1j75w.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> <83lh9djzb0.fsf@gnu.org> <565EAA75.7030308@gmx.at> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1449063993 5362 80.91.229.3 (2 Dec 2015 13:46:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Dec 2015 13:46:33 +0000 (UTC) Cc: mvoteiza@udel.edu, bruce.connor.am@gmail.com, emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 02 14:46:24 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 1a47jb-0006SI-BS for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 14:46:15 +0100 Original-Received: from localhost ([::1]:58165 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a47ja-0000DC-Ba for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 08:46:14 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a47iv-0008Ay-KT for emacs-devel@gnu.org; Wed, 02 Dec 2015 08:45:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a47iu-0002ex-IM for emacs-devel@gnu.org; Wed, 02 Dec 2015 08:45:33 -0500 Original-Received: from mtaout28.012.net.il ([80.179.55.184]:39181) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a47iu-0002eS-2n for emacs-devel@gnu.org; Wed, 02 Dec 2015 08:45:32 -0500 Original-Received: from conversion-daemon.mtaout28.012.net.il by mtaout28.012.net.il (HyperSendmail v2007.08) id <0NYQ00F00GTU2L00@mtaout28.012.net.il> for emacs-devel@gnu.org; Wed, 02 Dec 2015 15:44:34 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout28.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NYQ009JNGU9IP50@mtaout28.012.net.il>; Wed, 02 Dec 2015 15:44:34 +0200 (IST) In-reply-to: <565EAA75.7030308@gmx.at> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.184 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:195746 Archived-At: > Date: Wed, 02 Dec 2015 09:23:17 +0100 > From: martin rudalics > Cc: mvoteiza@udel.edu, emacs-devel@gnu.org > > >> 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? > > I'd blame the overlay mechanism. It worked just fine for me 2 days ago.