From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45824@debbugs.gnu.org, Alex Hutcheson <alexhutcheson@google.com>
Subject: bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color
Date: Wed, 20 Jan 2021 17:26:19 +0100 [thread overview]
Message-ID: <87czxzr2vo.fsf@gnus.org> (raw)
In-Reply-To: <83sg6w7mz4.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 19 Jan 2021 21:20:15 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I just don't see where that would end, that's all. Any
> terminal emulator can call itself anything, and Emacs cannot possibly
> know all the future names.
>
> But that's me; if Lars thinks we should have built-in support for this
> use case, I won't argue. I was just responding to his request for
> other opinions.
Even though it's a slippery slope adding more DWIM here, I think the
proposed tweak makes sense. It seems unlikely to break anything, and it
makes the common Emacs-under-screen case work better automatically.
So I think we should give it a go, but if it regresses anything, it
should be backed out again. Pushed now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-01-20 16:26 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 ` bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color Lars Ingebrigtsen
2021-01-19 15:34 ` 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 [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=87czxzr2vo.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45824@debbugs.gnu.org \
--cc=alexhutcheson@google.com \
--cc=eliz@gnu.org \
/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).