all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca,  rpluim@gmail.com,  emacs-devel@gnu.org
Subject: Re: Multi-tty
Date: Fri, 08 Nov 2024 13:25:42 +0100	[thread overview]
Message-ID: <m2bjyp29q1.fsf@gmail.com> (raw)
In-Reply-To: <86zfmand93.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Nov 2024 14:03:52 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: monnier@iro.umontreal.ca,  rpluim@gmail.com,  emacs-devel@gnu.org
>> Date: Fri, 08 Nov 2024 12:49:02 +0100
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > I have another suggestion: remove the support for COLORTERM entirely,
>> > or at least announce that it is not supported per-terminal.  It's high
>> > time terminals that support true color have their terminfo entries
>> > fixed and up-to-date.  We supported COLORTERM during the transition
>> > period, as a temporary kludge, to help people who had those terminals,
>> > but whose terminfo DB did not yet catch up, but we should slowly move
>> > towards removing that support from Emacs.
>> 
>> COLORTERM is used right now by popular programs (e.g. iTerm2) on my
>> system (macOS). So doing that is not an option for me.
>
> Why cannot those terminal have their terminfo entry set up with
> true-color support?

I don't know, you'd have to ask them.

> Anyway, as long as all of your client frames are on iTerm2, you should
> be fine.

Unless the support is removed, of course, which I hope it's not because
it's used in the wild.

And when you want to use an Emacs daemon, you also have to know that you
have to set COLORTERM for the daemon (iTerm2 for example does that
automatically in terminal windows but can't for a daemon of course), and
of course how to do it (tip: man launchd.plist). And then, you'll have
to remember to always use the right terminal emulator with the daemon,
while things just work with what I'm using now.

Quite unfortunate that all for "normal" users, IMO.



  reply	other threads:[~2024-11-08 12:25 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 ` Multi-tty Eli Zaretskii
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                 ` Gerd Möllmann [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2bjyp29q1.fsf@gmail.com \
    --to=gerd.moellmann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rpluim@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.