From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: jinx Date: Sat, 01 Apr 2023 08:56:10 +0300 Message-ID: <835yag16yt.fsf@gnu.org> References: <87sfdnyuxc.fsf@posteo.de> <83sfdl2z26.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20913"; mail-complaints-to="usenet@ciao.gmane.io" Cc: m.eliachevitch@posteo.de, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 01 07:56:26 2023 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 1piUDx-0005Eb-Rp for ged-emacs-devel@m.gmane-mx.org; Sat, 01 Apr 2023 07:56:25 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1piUDc-0006JT-Hs; Sat, 01 Apr 2023 01:56:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1piUDa-0006JG-Bi for emacs-devel@gnu.org; Sat, 01 Apr 2023 01:56:02 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1piUDZ-0006jF-Vk; Sat, 01 Apr 2023 01:56:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=heAM2Fhh3EGI6TrBs09IMUuJDnAMW5MfiaIgOA7YA/A=; b=gXzppS7yDkV0 JuxFBip+4W3iLTwk11GxYIrv8VVHhgPBFm1Pt38pGAuKCE3BYiVF9Qy8jDHtTB7Ib2t1cPu90r31o 0kvpzqwVuncJ00HXfpYu8+LYGi3t8PkR59Gu8fQ2q1OsfAq2r6S5a3JA4xbGgjeNxkyMOcKjob4Eu rg3GcYiIUPON7QknwyK64QQVM+Qyi9n91Ha35bHCd09BTci59Jno4WQTwM3J+74jbYRFuniNMq7F8 uD4WS7Mwo5jYrO3DwWQtDA3UvgpXmUGaeYeXA5QaBWPY5wLW0Z68bes8HZOMGzGPTM/ZiJ2pBCvuX Xy/iyaWa5PveG6FLjY73YA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1piUDS-0002C8-VY; Sat, 01 Apr 2023 01:55:55 -0400 In-Reply-To: (message from Richard Stallman on Fri, 31 Mar 2023 23:11:55 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304960 Archived-At: > From: Richard Stallman > Cc: m.eliachevitch@posteo.de, emacs-devel@gnu.org > Date: Fri, 31 Mar 2023 23:11:55 -0400 > > > jinx spell-checks the visible portion of the window. I don't see why > > we would need that. Suppose I scroll the window by 2 lines: why would > > I want the new visible portion to be spell-checked again, when the > > overlap with the last check is so large? > > You mean, it doesn't remember which part has already been checked? It seems to rely on JIT font-lock mechanism to keep track of what was already spell-checked. But my point was not about efficiency, it was about the user experience: why would I want to have the visible portion marked with mis-spelling indications at all times? This is not a natural way of dealing with spelling mistakes. And my main point was that if someone does want to have a mode or a command to mark spelling mistakes in a visible portion of the buffer, we can easily add that to the existing spell-checking commands and modes. No need to switch to a completely different implementation to have that feature.