From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: lax matching is not a great default behavior Date: Wed, 02 Dec 2015 09:23:17 +0100 Message-ID: <565EAA75.7030308@gmx.at> 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1449044623 12874 80.91.229.3 (2 Dec 2015 08:23:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Dec 2015 08:23:43 +0000 (UTC) Cc: mvoteiza@udel.edu, emacs-devel@gnu.org To: Eli Zaretskii , bruce.connor.am@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 02 09:23:39 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 1a42hO-0000eO-KY for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 09:23:38 +0100 Original-Received: from localhost ([::1]:56923 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a42hG-0002SI-TT for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 03:23:30 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42001) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a42hD-0002Pw-7L for emacs-devel@gnu.org; Wed, 02 Dec 2015 03:23:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a42hC-0000mq-Ez for emacs-devel@gnu.org; Wed, 02 Dec 2015 03:23:27 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:56243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a42hA-0000lM-Na; Wed, 02 Dec 2015 03:23:24 -0500 Original-Received: from [192.168.1.100] ([212.95.7.115]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MWwp6-1ZpnaQ2cOS-00W0P4; Wed, 02 Dec 2015 09:23:22 +0100 In-Reply-To: <83lh9djzb0.fsf@gnu.org> X-Provags-ID: V03:K0:LaLNrBzXowpSqaD9yV70Y5eNRjLNuRWhHeppPx05lFqVUJxIsaG KdPnjOBjzvQSCUHCQOVky4mVwR2ZWh0IfdVdxomOUDG3Fhe6T9fae7MXNpG2K2hrp8/9kPG AFY60bvPbyETrcu3jM+HGv6SrJhfq+kHyifPj+LsbhrU56NM27Sr7nNpMjBgUU9v/l7tqEH UXYRQda6aEtqzS0GtAKrA== X-UI-Out-Filterresults: notjunk:1;V01:K0:XmEzWXmf/3Y=:XB2yzNHBuroD6YZ4hT6Ta1 qzdCkbGxGCczp7ub1is1Emz3zZJ5caU+fmCOhj3UqXYhJZiMsKNndnNyE8ItJbaX3Lg/qq8FI xLGhtGYUhdeKA5CnorWYLpRWiVB47fRRjkF0rN32I3FOrVi6LOY3Yh1REv+mhxWN4wohU56MB gQkb5TjvQ/iTfnfcx6iTFFd3g7UcGTSPmSpqx6qqfZj1Z9WuZacPX8Y+g1GT00mPXQ3xjptDo FOk5ztrj65GNWCHo26kKakkazCQz2Gk0PMWcw4Zv1M1Xfqo9Q169CPU8uTgeOppH+ODZGJnn7 jzoG4uvFa2CIS0L/ZLhtLmTLViplqQZRVnoHTsvGXYldbSKE9gujYagPt5MZHQ158FICmXtpQ mGiF3E7nwfU770x7Q8dBjbP25JAnKtMsavJXKufoYqQ3GEpI/v0xW2V2mRa1xDPuB3YvxrSV0 5ojwIo08o0EVQZHEH0d6mLZRtEHHO6o0r+lCTW205tPvE6Ns9xiBTgmJMyHbS5Ba/VOjClm7B HH8U9mCkMY506DymBXMhs4+f3oNbf2/0+5zbf83sFDEQui6p3NrgVoVbOXWm3x79j+b4XaToe 7ko8rfgmlAMf9714rRCuOvwts6yRVWKgkiW9pl/5CkuDTisytTJjKyAJcGmPNO4R+X2FoYSrQ 1IupjlE9lSqutKrT+7cuxFpMUx4AuDihV80OfHVHpG4OlXlcsudboTWy8T4klMJgTCnCK+ef5 52ax7bj4WApamUwcGkoS5IDEXMpi6kQlEIdy+2F1u4aRh1PTNsNJDZCAffcp8Eihzp7LM0yd X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.20 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:195733 Archived-At: >> 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. martin