From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: bug-reference-prog-mode slows down CC Mode's scrolling by ~7% Date: Fri, 03 Sep 2021 08:30:28 -0400 Message-ID: References: <838s0eyyjg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13253"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Alan Mackenzie , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 03 14:38:38 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mM8Ss-0003FT-98 for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Sep 2021 14:38:38 +0200 Original-Received: from localhost ([::1]:34234 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mM8Sq-000115-UD for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Sep 2021 08:38:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36942) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mM8LC-0008Vb-9e for emacs-devel@gnu.org; Fri, 03 Sep 2021 08:30:44 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:5218) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mM8L6-0002S3-R7; Fri, 03 Sep 2021 08:30:40 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D9DC44403E0; Fri, 3 Sep 2021 08:30:33 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id AAEA0440345; Fri, 3 Sep 2021 08:30:32 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1630672232; bh=6nqHe+p7PF7PSungPDEQOf3PGF8xU0UyLRe0xpoA53s=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=FW9byu8RpiHLci3BVZX3mGcHJrkAXxQ5oWJ/cvFMcqko2NzCnipvfenQKWpB7JNa5 dOlKdxo6jrU1p/naFgMhe0VyJ1yP1ZQ80fEUidf3Rxojp6+uI+BTEg9wKEqsQ6V+0M jHFxFnBYxbbKoN8mGYlm9cjnnlbJ+LZ1BlwbIP9dkUR57EkRtqCvMydw5YPe8QXPWF PZfpk6wwfCwzAwvsfSPah3bpEEU+hYMJCuUg39fvdVJOL8yb3TL3oZnx9Kpjvf1yQu qUr8sOQINsA3Wj+lxEChGiuZHQdxHcnoD4Ra/VtyvKzybO0VWPGvwyxyZCer4YTJOn NVvtKW71cQ/Sw== Original-Received: from milanesa (unknown [104.247.244.135]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 49C44120296; Fri, 3 Sep 2021 08:30:32 -0400 (EDT) In-Reply-To: <838s0eyyjg.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 03 Sep 2021 09:16:03 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273786 Archived-At: > More importantly, this cannot hide in a comment, it must be clearly > documented, both in doc strings and in the ELisp manual. (Assuming > this is the change we will go with, of course.) I don't understand why you think so. It's a detail that should be purely internal to jit-lock.el (and which should have no impact other than in terms of performance). E.g. it shouldn't affect those people writing packages which rely on jit-lock (it doesn't change the rules of what to return in `jit-lock-bounds`, for instance). Stefan