unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Al Petrofsky <al@petrofsky.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64075@debbugs.gnu.org, gregory@heytings.org
Subject: bug#64075: 28.2; ispell broken on uncolored terminals
Date: Thu, 15 Jun 2023 02:34:48 -0400	[thread overview]
Message-ID: <CAPMQwz5EQ_bw-n9_97X6zM57OgJrm67CMMSbwGsfQWh51KaPAQ@mail.gmail.com> (raw)
In-Reply-To: <835y7puw0z.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

I apologize if I'm misunderstanding things.  I'm certainly not
suggesting removing any functionality that is useful on old monochrome
ttys.  The reason I became aware of this bug is that I am using a
monochrome tty.

> > Still, this anachronistic kludge should really be nuked entirely.

> Why?  And what's "anachronistic" about that code?

What's anachronistic about that code (meaning the
ispell-highlight-spelling-error-generic function) is that it uses a
kludge that made it possible in pre-version-21 emacs to get some text
displayed in inverse video on a tty even though emacs could not
display faces on ttys.  But since Emacs 21, on any tty that has a
termcap "so" capability, you can get inverse-video simply by using an
inverse-video face.

So I don't think ispell-highlight-spelling-error-generic currently
provides any functionality that isn't more conveniently and
maintainably provided by ispell-highlight-spelling-error-overlay, with
the additional benefit that the user can, if he wants, customize
ispell-highlight-face to something other than inverse-video.

(Making the default isearch face (and therefore the default
ispell-highlight-face) be blue-on-magenta on color terminals but
inverse-video on monochrome terminals is already handled
automatically.)

[-- Attachment #2: Type: text/html, Size: 1546 bytes --]

  reply	other threads:[~2023-06-15  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 23:13 bug#64075: 28.2; ispell broken on uncolored terminals Al Petrofsky
2023-06-14 23:25 ` Gregory Heytings
2023-06-14 23:48   ` Al Petrofsky
2023-06-15  5:36     ` Eli Zaretskii
2023-06-15  6:34       ` Al Petrofsky [this message]
2023-06-15  7:48         ` Eli Zaretskii
2023-06-15 23:19           ` Al Petrofsky
2023-06-16  6:27             ` Eli Zaretskii
2023-06-15  5:23   ` Eli Zaretskii

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=CAPMQwz5EQ_bw-n9_97X6zM57OgJrm67CMMSbwGsfQWh51KaPAQ@mail.gmail.com \
    --to=al@petrofsky.org \
    --cc=64075@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.org \
    /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).