unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Kuraj <ivanko@csail.mit.edu>
Cc: 62876@debbugs.gnu.org
Subject: bug#62876: 28.2; strikethrough text on TTY not showing
Date: Sun, 16 Apr 2023 09:19:01 +0300	[thread overview]
Message-ID: <83pm84bb8q.fsf@gnu.org> (raw)
In-Reply-To: <913550lj8f.fsf@csail.mit.edu> (message from Ivan Kuraj on Sat, 15 Apr 2023 21:11:00 -0400)

merge 62876 62265
thanks

> From: Ivan Kuraj <ivanko@csail.mit.edu>
> Date: Sat, 15 Apr 2023 21:11:00 -0400
> 
> 
> Strikethrough text is not displaying properly when Emacs is started with `emacs -nw`. I tried xterm (Arch Linux), iTerm2 (MacOS), xterm/iterm2 over ssh. Tried Emacs 28.2 (Linux/Macos, with/without native compilation, with/without Doom Emacs).
> 
> On xterm strikethrough is underlined. Terminals, as well as GUI Emacs, properly display strikethrough. (Terminals on executing `echo -e "\e[9mstrikethrough\e[0m"`.) TERM is set so that the terminals confirm support for "smxx":
> > $ TERM=xterm-24bit infocmp -x | grep -E '(rm|sm)xx'
> > 79:     kpZRO=\EOp, rmxx=\E[29m,
> > 82:     smxx=\E[9m, xm=\E[<%i%p3%d;%p1%d;%p2%d;%?%p4%tM%em%;,
> 
> If I am not mistaken, this was working properly on prior versions of Emacs. (As confirmed, e.g. here: https://emacs.stackexchange.com/questions/43722/emacsclient-nw-and-strikethrough-text-in-org-mode)

This is a duplicate of bug#62265, for which I just installed a fix on
the emacs-29 branch.  Please try that branch if you can.

P.S. Support for strikethrough on TTY frames was added to Emacs in
version 28.1.





      parent reply	other threads:[~2023-04-16  6:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16  1:11 bug#62876: 28.2; strikethrough text on TTY not showing Ivan Kuraj
2023-04-16  5:14 ` Jim Porter
2023-04-16  6:25   ` Eli Zaretskii
2023-04-16 17:55     ` Ivan Kuraj
2023-04-16 19:02       ` Eli Zaretskii
2023-04-16  6:19 ` Eli Zaretskii [this message]

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=83pm84bb8q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62876@debbugs.gnu.org \
    --cc=ivanko@csail.mit.edu \
    /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).