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 10:20:10 +0300 Message-ID: <83sfdkysph.fsf@gnu.org> References: <87sfdnyuxc.fsf@posteo.de> <83sfdl2z26.fsf@gnu.org> <86tty0ydnl.fsf@gnu.org> <83fs9k20tu.fsf@gnu.org> <86edp4yarm.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8659"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, m.eliachevitch@posteo.de, emacs-devel@gnu.org To: Arash Esbati Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 01 09:20:24 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 1piVXD-00025R-Pw for ged-emacs-devel@m.gmane-mx.org; Sat, 01 Apr 2023 09:20:23 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1piVWu-0001iD-8f; Sat, 01 Apr 2023 03:20: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 1piVWs-0001i0-0E for emacs-devel@gnu.org; Sat, 01 Apr 2023 03:20: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 1piVWq-0003R4-NP; Sat, 01 Apr 2023 03:20:00 -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=A5YCOfk/f9vAoc+ox2t6XVPhYMKKEx8P7udlPEn607U=; b=aZ5WcMEui6yN g0D0HRXaqkFjYHhcqOloZ6OON5YGnMsDbf5gGUTUo7gOFjovm4k/BC2kgUoYzxWaDVB1nTKY7XMUi eOivk695CZAa4okQZagTI9O7+y+tHUHTtsdBej/nMol5vn4p7g3MyLkbDEHDApyDNKzVpd6Qs8lFI JVMe9xjT6hlFzLpYn3P3jmOmuRJ6b8bquXOfk/TacZvz8A6phMeSoDF48r4w+KnPvw8zbnK7veUzi hdHcH6gx+zbf/Pxjlt+VRUD3sKN9lXRRxgxFh2Y+Y0n5lWLIAUG3pkWkz5HqWjATz6PlKCvTPKDLg MacvILJA3jRWehtqRyisaw==; 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 1piVWk-0005He-93; Sat, 01 Apr 2023 03:19:54 -0400 In-Reply-To: <86edp4yarm.fsf@gnu.org> (message from Arash Esbati on Fri, 31 Mar 2023 21:35:25 +0200) 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:304974 Archived-At: > From: Arash Esbati > Cc: rms@gnu.org, m.eliachevitch@posteo.de, emacs-devel@gnu.org > Date: Fri, 31 Mar 2023 21:35:25 +0200 > > > (I wonder why the built-in TeX support in the spell-checker doesn't do > > this job, it's supposed to be adequate, and all Emacs needs to do is > > to tell the speller it is working on TeX text. So I don't even > > understand why we need to skip something on our own in these cases.) > > I can only tell for hunspell: It has built-in support for skipping of > many macro arguments and environments[1], but: > > a) It is not complete (and probably will never be) > b) It cannot work for user defined macros/environments, and this is > where AUCTeX/ispell shine: AUCTeX can parse user defined > macros/environments and add them automatically to > `ispell-tex-skip-alists'. > c) Another advantage of `ispell-tex-skip-alists' is that one can write > a function and put that in `ispell-tex-skip-alists' for certain > macros/environments: That gives us a lot of flexibility to precisely > skip or check. These issues are not TeX-specific, so they should be handled in a more general way, not bound to TeX/LaTeX. In particular, any "tex-skip" features should not supplant the TeX support built into the speller, they should only _add_ skip regexps for stuff that the speller cannot support, like user-defined macros. I'm not sure I understand item c), though: when and why would one want to spell-check macros and environments?