From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Reuben Thomas via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period Date: Mon, 14 Feb 2022 17:01:09 +0000 Message-ID: References: <87pp5az1u7.fsf@sc3d.org> <83twumnem2.fsf@gnu.org> <83iob1nxfb.fsf@gnu.org> <87o83bxhll.fsf@gnus.org> <83fsonq6w9.fsf@gnu.org> <83k0dxpo5f.fsf@gnu.org> <83ee45pj7r.fsf@gnu.org> <83czjppfh1.fsf@gnu.org> Reply-To: Reuben Thomas Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a6062e05d7fd5d8d" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16332"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, 20741@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 14 18:09:31 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1nJeqw-00042r-OG for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 14 Feb 2022 18:09:31 +0100 Original-Received: from localhost ([::1]:47692 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nJequ-00075a-Rj for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 14 Feb 2022 12:09:28 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:46384) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJeji-00009g-U1 for bug-gnu-emacs@gnu.org; Mon, 14 Feb 2022 12:02:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48531) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nJeji-0004uU-Hf for bug-gnu-emacs@gnu.org; Mon, 14 Feb 2022 12:02:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nJeji-0000Eb-FC for bug-gnu-emacs@gnu.org; Mon, 14 Feb 2022 12:02:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Reuben Thomas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 14 Feb 2022 17:02:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20741 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed Original-Received: via spool by 20741-submit@debbugs.gnu.org id=B20741.1644858091864 (code B ref 20741); Mon, 14 Feb 2022 17:02:02 +0000 Original-Received: (at 20741) by debbugs.gnu.org; 14 Feb 2022 17:01:31 +0000 Original-Received: from localhost ([127.0.0.1]:42428 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nJejC-0000Ds-Go for submit@debbugs.gnu.org; Mon, 14 Feb 2022 12:01:30 -0500 Original-Received: from mail-pf1-f169.google.com ([209.85.210.169]:36570) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nJej9-0000Dd-MW for 20741@debbugs.gnu.org; Mon, 14 Feb 2022 12:01:29 -0500 Original-Received: by mail-pf1-f169.google.com with SMTP id z16so8369862pfh.3 for <20741@debbugs.gnu.org>; Mon, 14 Feb 2022 09:01:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sc3d.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4sLxnDDOvXQohZOVabqJdirq95f44IWTPCb7NprPkDM=; b=LUfCJH5wYkGRX7I/czn/ThgeQbA9/NApTIcHwExTx1fc5kwmBUiKsJWLa1sSuUjyv0 WWjmwcHcHZU2/b2KGB6BQI03F4oIMJmeeI0CY+fIxuHwTiKZHt9LK33v2PTkAK63YKqp ZOQIhrkw5lEHCpZC+IiluB5yb3TpS1ZREZP+o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4sLxnDDOvXQohZOVabqJdirq95f44IWTPCb7NprPkDM=; b=fhuPe5CTXGljf57ESiPv1hw9Cjg/w/QX0aRtp56VW43NVR9/bzyeD1i026yQ5VLmN5 x3z90XBlhSjhF0nX4RQSt5paNoVPcq+I3iLBUFMOE84CAaVUCtQLzIUAhay12yY3gY5S UMJJ+Md6vF/wSj6UttD2+SCl48gv+9HjSzNJ5U6yLzluD+hFMPDz2bCLj80BXLY/l3Rk CodqcLB+MWiEUDoS0jjOkagPID9sHxZhZk0CpbZOiVpPG2zkiEULJOAR+w1l8UjjfffQ NETJEHeq1m3GpvaPjWd7t4VdDwDEKMgk0PknQ1FIZ+5rCkow9bd9P6nZYnDEsOiQPAn+ hv0g== X-Gm-Message-State: AOAM530ZxIV8QDF5QfLZD4MvJbNhtDXMV1Ow5mK7uAmE5gJO/FbYP/T9 WfMg8tCocpdH7eGNR9IfMzGgoVMNo4AF7bMP+dH8fA== X-Google-Smtp-Source: ABdhPJxdVt6Si6YZkKgwsWIkCxAhEpAu4dfiFS5zVqhLvc+tr/ZhZCoLGchukOfZdtjYb5pWLTaEQGi7pipRixhxVCU= X-Received: by 2002:a65:5c48:: with SMTP id v8mr520982pgr.343.1644858081405; Mon, 14 Feb 2022 09:01:21 -0800 (PST) In-Reply-To: <83czjppfh1.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:226906 Archived-At: --000000000000a6062e05d7fd5d8d Content-Type: text/plain; charset="UTF-8" On Mon, 14 Feb 2022 at 16:42, Eli Zaretskii wrote: > > From: Reuben Thomas > > > > I think we can distinguish 3 different problems here: > > > > 1. Natural language spellchecking. That's what this issue is about. > > 2. Spell-checking code. (Essentially, identifiers.) > > 3. Finding code inside natural language, and checking it as if it were > code. (That's what you're talking about > > here.) This is not a spellchecking problem, it's a problem of > identifying which spell-checking apparatus to > > use, rather like font-lock for multi-language buffers. It's hard to see > how to do it without some syntactic clue > > (e.g. the use of backticks in markdown), as used in multi-language > buffers for font-locking. > > Anyway: what are the practical proposals for improving this? Are we > going to handle only periods, or does anyone have a more general > solution? > Emacs does not currently try to handle case 3, as far as I know. That would be a medium-sized project in its own right. Case 2 depends on per-programming-language syntax tables, not on the spellchecker. I don't know what the current arrangements for this are. Case 1, on which everything else depends, is a matter of Emacs sending stretches of text to the spell-checker, which currently (at least with Hunspell) does not deal with punctuation very well, though there are plans to improve Hunspell, according to the issue I linked to earlier. None of these would benefit from special-casing treatment of the period or any other character in ispell.el, I think. -- https://rrt.sc3d.org --000000000000a6062e05d7fd5d8d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, 14 Feb 2022 at 16:42, Eli Zaret= skii <eliz@gnu.org> wrote:
> From: Reu= ben Thomas <rrt@sc3d.o= rg>
>
> I think we can distinguish 3 different problems here:
>
> 1. Natural language spellchecking. That's what this issue is about= .
> 2. Spell-checking code. (Essentially, identifiers.)
> 3. Finding code inside natural language, and checking it as if it were= code. (That's what you're talking about
> here.) This is not a spellchecking problem, it's a problem of iden= tifying which spell-checking apparatus to
> use, rather like font-lock for multi-language buffers. It's hard t= o see how to do it without some syntactic clue
> (e.g. the use of backticks in markdown), as used in multi-language buf= fers for font-locking.

Anyway: what are the practical proposals for improving this?=C2=A0 Are = we
going to handle only periods, or does anyone have a more general
solution?

Emacs does not cu= rrently try to handle case 3, as far as I know. That would be a medium-size= d project in its own right.

Case 2 depends on per-programming-language syntax tables, not on the = spellchecker. I don't know what the current arrangements for this are.<= /div>

Case 1, on which every= thing else depends, is a matter of Emacs sending stretches of text to the s= pell-checker, which currently (at least with Hunspell) does not deal with p= unctuation very well, though there are plans to improve Hunspell, according= to the issue I linked to earlier.

None of these would benefit from special-casing treatment of t= he period or any other character in ispell.el, I think.

= --
--000000000000a6062e05d7fd5d8d--