From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Multi-tty
Date: Thu, 07 Nov 2024 12:58:33 +0200 [thread overview]
Message-ID: <8634k3qpie.fsf@gnu.org> (raw)
In-Reply-To: <m24j4jjrp6.fsf@gmail.com> (message from Gerd Möllmann on Thu, 07 Nov 2024 10:53:09 +0100)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Thu, 07 Nov 2024 10:53:09 +0100
>
> I was playing with multi-tty today, and I encountered strange behavior.
> For example, using 2 terminals that have different capabilties, say
> different TERM and/or COLORTERM, does not really work.
>
> (Informal example: I start an emacs server -nw in iTerm
> (TERM=xterm-256color, COLORTERM=truecolor), then emacsclient --tty in a
> Terminal window (TERM=xterm, COLORTERM not set) => The Emacs frame in
> the Terminal window is obviously confused about the terminal's
> color capabilties.)
>
> Is something like that worth writing a bug report? Or maybe it's already
> known, although I can't find anything in Debbugs?
This is simply not supported, never was. The environment variables
are not per-terminal, so their effect is global, and the way we
process them (and have no other way) is that the environment variables
override what terminfo tells us.
We support these environment variables only as poor-man's terminfo,
for when terminfo doesn't tell us the whole truth, or the user "wants
more". So what you should do is not set any such environment
variables at all, and let Emacs deduce the terminal capabilities from
the name of the terminal.
next prev parent reply other threads:[~2024-11-07 10:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 9:53 Multi-tty Gerd Möllmann
2024-11-07 10:58 ` Eli Zaretskii [this message]
2024-11-07 11:15 ` Multi-tty Robert Pluim
2024-11-07 11:38 ` Multi-tty Gerd Möllmann
2024-11-07 11:47 ` Multi-tty Eli Zaretskii
2024-11-08 8:18 ` Multi-tty Gerd Möllmann
2024-11-08 8:28 ` Multi-tty Gerd Möllmann
2024-11-08 8:50 ` Multi-tty Eli Zaretskii
2024-11-08 9:16 ` Multi-tty Gerd Möllmann
2024-11-08 9:42 ` Multi-tty Gerd Möllmann
2024-11-08 10:17 ` Multi-tty Robert Pluim
2024-11-08 11:09 ` Multi-tty Gerd Möllmann
2024-11-08 11:49 ` Multi-tty Eli Zaretskii
2024-11-08 11:43 ` Multi-tty Eli Zaretskii
2024-11-08 11:41 ` Multi-tty Eli Zaretskii
2024-11-08 11:49 ` Multi-tty Gerd Möllmann
2024-11-08 12:03 ` Multi-tty Eli Zaretskii
2024-11-08 12:25 ` Multi-tty Gerd Möllmann
2024-11-08 12:11 ` Multi-tty Robert Pluim
2024-11-08 12:29 ` Multi-tty Gerd Möllmann
2024-11-08 13:53 ` Multi-tty Stefan Monnier
2024-11-08 13:55 ` Multi-tty Eli Zaretskii
2024-11-08 14:05 ` Multi-tty Gerd Möllmann
2024-11-08 14:11 ` Multi-tty Gerd Möllmann
2024-11-08 15:42 ` Multi-tty Yuri Khan
2024-11-08 13:55 ` Multi-tty Stefan Monnier
2024-11-08 14:24 ` Multi-tty Robert Pluim
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=8634k3qpie.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@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).