unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Stefan Kangas <stefan@marxist.se>, Eli Zaretskii <eliz@gnu.org>
Cc: 23097@debbugs.gnu.org
Subject: bug#23097: 24.5; ispell.el: lines with both CASECHARS and NOT-CASECHARS get sent to the spell checker
Date: Mon, 17 Aug 2020 12:20:08 +0300	[thread overview]
Message-ID: <5fe8e18f-efb4-4f9b-fd85-0cb4eccc58b4@gmail.com> (raw)
In-Reply-To: <CADwFkmmkuh96=FJuX15LC+zcgNBpMJW6d+3hDb7UsSfzkdS85g@mail.gmail.com>

This is not an external software bug, but very much an Emacs bug.

I'm not sure what was the initial design idea for CASECHARS and 
NOT-CASECHARS, but whatever it was, it would not work effectively due to 
feeding the entire line. The most obvious practical use for them(being 
able to spellcheck languages with completely different alphabets without 
the spellchecker misfiring on either pass) would not work either.

The ideal pratical fix for this should spellcheck such lines word by word.

-- 
Best Regards,
Nikolay Kudryavtsev






  reply	other threads:[~2020-08-17  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 18:11 bug#23097: 24.5; ispell.el: lines with both CASECHARS and NOT-CASECHARS get sent to the spell checker Nikolay Kudryavtsev
2016-03-23 18:22 ` Eli Zaretskii
2016-03-23 20:12   ` Nikolay Kudryavtsev
2020-08-15  4:22   ` Stefan Kangas
2020-08-15 16:15     ` Eli Zaretskii
2020-08-15 16:40       ` Stefan Kangas
2020-08-17  9:20         ` Nikolay Kudryavtsev [this message]
2020-08-17 12:48           ` Stefan Kangas
2020-08-17 16:40           ` Eli Zaretskii
     [not found]             ` <08f3ac29-761c-ced7-1e2f-0f643512b986@gmail.com>
2020-10-13 17:00               ` Eli Zaretskii
     [not found]               ` <83mu0q132o.fsf@gnu.org>
2020-10-14 19:20                 ` Nikolay Kudryavtsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5fe8e18f-efb4-4f9b-fd85-0cb4eccc58b4@gmail.com \
    --to=nikolay.kudryavtsev@gmail.com \
    --cc=23097@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefan@marxist.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).