unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Kuraj <ivanko@csail.mit.edu>
To: Eli Zaretskii <eliz@gnu.org>, Jim Porter <jporterbugs@gmail.com>
Cc: 62876@debbugs.gnu.org
Subject: bug#62876: 28.2; strikethrough text on TTY not showing
Date: Sun, 16 Apr 2023 13:55:52 -0400	[thread overview]
Message-ID: <4A43FE77-DE3B-4AEA-B03C-EFAD4F292A09@csail.mit.edu> (raw)
In-Reply-To: <83mt38baxb.fsf@gnu.org>

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

Oh I see. Understood.

Tested on emacs29 branch -- it's fine now, strikethrough indeed renders properly on that one.

On April 16, 2023 2:25:52 AM EDT, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 15 Apr 2023 22:14:30 -0700
>> From: Jim Porter <jporterbugs@gmail.com>
>> 
>> On 4/15/2023 6:11 PM, Ivan Kuraj wrote:
>> > 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).
>> 
>> Is this a dupe of bug#62265? (The bug title says it's about underline, 
>> but it's really about strikethrough.) You could try the patch there and 
>> see if it helps.
>
>We've dropped the ball on that bug.  I've now installed the fix
>discussed there, so this should be solved on the emacs-29 branch.

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

  reply	other threads:[~2023-04-16 17:55 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 [this message]
2023-04-16 19:02       ` Eli Zaretskii
2023-04-16  6:19 ` 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=4A43FE77-DE3B-4AEA-B03C-EFAD4F292A09@csail.mit.edu \
    --to=ivanko@csail.mit.edu \
    --cc=62876@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jporterbugs@gmail.com \
    /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).