From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alex Hutcheson <alexhutcheson@google.com>
Cc: 45824@debbugs.gnu.org
Subject: bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color
Date: Tue, 19 Jan 2021 07:51:11 +0100 [thread overview]
Message-ID: <877do9mnc0.fsf@gnus.org> (raw)
In-Reply-To: <u49xpn2a7za1.fsf@alexh.c.googlers.com> (Alex Hutcheson's message of "Tue, 12 Jan 2021 14:04:06 -0500")
Alex Hutcheson <alexhutcheson@google.com> writes:
> In some common configurations, GNU Screen sets
> TERM=screen.xterm-256color.
[...]
> The TERM parsing logic is documented at
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Terminal_002dSpecific.html
> and the code is in `tty-find-type` within lisp/faces.el
>
> The simple fix would be to also consider periods to be a valid separator
> within this logic.
That does sound like a simple fix. :-) Are there any common TERM
values that have dots in them, though? It does seem unlikely, in which
case this simple fix should probably work?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-01-19 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:04 bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 19:22 ` bug#45824: Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 6:51 ` Lars Ingebrigtsen [this message]
2021-01-19 15:34 ` bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color alexhutcheson--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 15:56 ` Lars Ingebrigtsen
2021-01-19 16:52 ` alexhutcheson--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 18:27 ` Eli Zaretskii
2021-01-19 18:33 ` alexhutcheson--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 19:20 ` Eli Zaretskii
2021-01-20 16:26 ` Lars Ingebrigtsen
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=877do9mnc0.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45824@debbugs.gnu.org \
--cc=alexhutcheson@google.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).