From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 65029@debbugs.gnu.org, james.ipswich@proton.me
Subject: bug#65029: Italics bug when Emacs runs inside GNU Screen
Date: Sat, 19 Aug 2023 14:12:09 +0300 [thread overview]
Message-ID: <83jztrz3p2.fsf@gnu.org> (raw)
In-Reply-To: <387ee04aa97c8639f227@heytings.org> (message from Gregory Heytings on Sat, 19 Aug 2023 10:57:29 +0000)
> Date: Sat, 19 Aug 2023 10:57:29 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: james.ipswich@proton.me, 65029@debbugs.gnu.org
>
> > Maybe that change is not yet distributed in the version of screen you
> > have installed, Gregory?
> >
>
> I have a fairly recent version:
>
> $ screen --version
> Screen version 4.09.00 (GNU) 30-Jan-22
>
> A few messages were recently added to the ticket James mentioned:
>
> https://savannah.gnu.org/bugs/?func=detailitem&item_id=36676
>
> which IIUC mean that this issue will actually be fixed only in Screen
> 5.0.0, which will be released next year. However, I just built the latest
> version of Screen (master), and the problem is still present AFAICS.
And their version from master also yields the same result from
infocmp? If so, in what way they "implemented" support for italics?
Should the terminfo database be perhaps updated when you install a
newer version of Screen?
next prev parent reply other threads:[~2023-08-19 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 23:37 bug#65029: Italics bug when Emacs runs inside GNU Screen James Ipswich via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 6:46 ` Eli Zaretskii
2023-08-12 6:45 ` Eli Zaretskii
2023-08-19 8:20 ` Eli Zaretskii
2023-08-19 9:36 ` Gregory Heytings
2023-08-19 10:40 ` Eli Zaretskii
2023-08-19 10:57 ` Gregory Heytings
2023-08-19 11:12 ` Eli Zaretskii [this message]
2023-08-19 11:27 ` Gregory Heytings
2023-08-19 11:31 ` Gregory Heytings
2023-08-19 11:32 ` Eli Zaretskii
2023-08-19 11:40 ` Eli Zaretskii
2023-08-19 12:14 ` Andreas Schwab
2023-08-19 12:23 ` Gregory Heytings
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=83jztrz3p2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65029@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=james.ipswich@proton.me \
/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).