From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: 75024@debbugs.gnu.org
Cc: Mohsin Kaleem <mohkale@kisara.moe>
Subject: bug#75024: [PATCH] Fix check for underlining capability on ttys
Date: Sun, 05 Jan 2025 05:08:07 +0100 [thread overview]
Message-ID: <m25xmtx5qw.fsf@gmail.com> (raw)
In-Reply-To: <m2ttauj0lm.fsf@gmail.com> ("Gerd Möllmann"'s message of "Mon, 23 Dec 2024 08:54:29 +0100")
Hi Mohsin, friendly ping. Could you find the time to look at this?
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>>
>>> Tags: patch
>>
>> Please disregard the patch. I'll send another one later.
>
> I meanwhile found this, to my great surprise:
>
> #define TTY_CAP_UNDERLINE_STYLED (0x32 & TTY_CAP_UNDERLINE)
>
> That makes TTY_CAP_UNDERLINE_STYLED == TTY_CAP_UNDERLINE. And this test
> in tty_capable_p
>
> TTY_CAPABLE_P_TRY (tty,
> TTY_CAP_UNDERLINE, tty->TS_enter_underline_mode,
> NC_UNDERLINE);
> TTY_CAPABLE_P_TRY (tty,
> TTY_CAP_UNDERLINE_STYLED, tty->TF_set_underline_style,
>
> fails because it tests TTY_CAP_UNDERLINE twice, and requires both
> TS_enter_underline_mode and TF_set_underline_style to be usable for
> underline support. In Terminal.app, only TS_enter_underline_mode is
> available.
>
> Maybe this should have been
>
> #define TTY_CAP_UNDERLINE_STYLED 0x40
>
> ?
>
> BTW, the 0x32 also also makes no sense to me because of
>
> #define TTY_CAP_ITALIC 0x10
> #define TTY_CAP_STRIKE_THROUGH 0x20
>
> CC to the original author to check.
next prev parent reply other threads:[~2025-01-05 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 13:13 bug#75024: [PATCH] Fix check for underlining capability on ttys Gerd Möllmann
2024-12-23 5:52 ` Gerd Möllmann
[not found] ` <m2ttauj0lm.fsf@gmail.com>
2025-01-05 4:08 ` Gerd Möllmann [this message]
2025-01-05 11:36 ` Mohsin Kaleem
2025-01-05 11:48 ` Gerd Möllmann
2025-01-05 11:53 ` Mohsin Kaleem
2025-01-05 11:54 ` Gerd Möllmann
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=m25xmtx5qw.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=75024@debbugs.gnu.org \
--cc=mohkale@kisara.moe \
/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).