From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: State of the overlay tree branch? Date: Fri, 23 Mar 2018 08:55:59 -0400 Message-ID: References: <834lldp18f.fsf@gnu.org> <9646341d-700b-4240-216b-8c0e753fa79f@arkona-technologies.de> <86d03e78-9984-f33e-a3f3-3faa4b34d78b@arkona-technologies.de> <83vadso9ad.fsf@gnu.org> <5155d5e2-6b5c-581e-89fe-4f3af717304f@arkona-technologies.de> <4c82fcbd-961a-c6ca-b1f0-6b85665cb339@arkona-technologies.de> <83o9jfi5a9.fsf@gnu.org> <83efkbi2hb.fsf@gnu.org> <83a7uzhsmz.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1521809683 4820 195.159.176.226 (23 Mar 2018 12:54:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 23 Mar 2018 12:54:43 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 23 13:54:38 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ezMDO-0001AX-NK for ged-emacs-devel@m.gmane.org; Fri, 23 Mar 2018 13:54:38 +0100 Original-Received: from localhost ([::1]:37941 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezMFS-0001V3-1z for ged-emacs-devel@m.gmane.org; Fri, 23 Mar 2018 08:56:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42678) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezMEo-0001Ut-DG for emacs-devel@gnu.org; Fri, 23 Mar 2018 08:56:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ezMEl-0008Ab-BP for emacs-devel@gnu.org; Fri, 23 Mar 2018 08:56:06 -0400 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:45533) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezMEl-00088w-5i; Fri, 23 Mar 2018 08:56:03 -0400 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id w2NCtx0a023071; Fri, 23 Mar 2018 08:56:00 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 9FE2160223; Fri, 23 Mar 2018 08:55:59 -0400 (EDT) In-Reply-To: <83a7uzhsmz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Mar 2018 15:40:36 +0300") X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 2 Rules triggered EDT_SA_DN_PASS=0, RV6249=0 X-NAI-Spam-Version: 2.3.0.9418 : core <6249> : inlines <6514> : streams <1782030> : uri <2613393> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:223961 Archived-At: > I'm not sure, because the profile indicates memrchr is a significant > runner-up in the CPU time usage. Oh, indeed I wasn't clear: it won't solve the "too many markers" case, but it will still be useful, especially in the case where there aren't too many markers. My experience with nlinum--line-number-at-pos is that it's a low-hanging fruit. If the solution can be implemented directly inside line-number-at-pos it'd be even better. Stefan