From: Dan Nicolaescu <dann@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eric.hanchrow@gmail.com, 22154@debbugs.gnu.org
Subject: bug#22154: 25.0.50; emacsclient -c "breaks" 256-color display in server
Date: Mon, 14 Dec 2015 11:39:39 -0500 [thread overview]
Message-ID: <yxq37v5yofo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83a8pd3txg.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 14 Dec 2015 17:56:43 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Dan Nicolaescu <dann@gnu.org>
>> Cc: Eric Hanchrow <eric.hanchrow@gmail.com>, 22154@debbugs.gnu.org
>> Gcc: nnml+archive:sent-mail-2015
>> Date: Mon, 14 Dec 2015 01:21:26 -0500
>>
>> Using different number of colors on different ttys should work.
>> I just tried it briefly, and it works fine on my Fedora machine with
>> 24.5.
>> I don't have a very recent version compiled.
>>
>> You can try it with
>> $ emacs -Q -f server-start&
>> Then from an xterm: emacsclient -t
>> And then from a different one: env TERM=vt100 emacsclient -t
>>
>> The frame in the first xterm should display some colors, the one in the
>> second should be b&w...
>
> This simple use case indeed (almost) works. (To have it work better,
> you need the patch I posted here.) But in general, the current
> implementation doesn't support this, AFAICT, for 2 reasons:
What exactly is the problem that your patch fixes?
I don't remember all the details, but having multiple terminal frames
running on multiple kinds of terminals, with different color depths and
even background modes was heavily tested when the multi-tty work was
going on. One of the usual tests was to have rxvt with both 8 and 256
colors and white on black and black on white (rxvt not xterm because
rxvt sets an environment variable with the default color and emacs can
decide if it's a light or dark background based on that). It worked
fine.
Did something break meanwhile or you are dealing with some new thing
that was not dealt with back then?
Thanks
--Dan
next prev parent reply other threads:[~2015-12-14 16:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 21:49 bug#22154: 25.0.50; emacsclient -c "breaks" 256-color display in server Eric Hanchrow
2015-12-13 17:30 ` Eli Zaretskii
2015-12-13 18:05 ` Eric Hanchrow
2015-12-13 18:17 ` Eli Zaretskii
2015-12-13 18:37 ` Eli Zaretskii
2015-12-13 18:47 ` Eric Hanchrow
2015-12-13 19:51 ` Eli Zaretskii
2015-12-13 20:26 ` Eric Hanchrow
2015-12-13 20:49 ` Eli Zaretskii
2015-12-14 6:21 ` Dan Nicolaescu
2015-12-14 15:56 ` Eli Zaretskii
2015-12-14 16:39 ` Dan Nicolaescu [this message]
2015-12-14 17:02 ` Eli Zaretskii
2015-12-15 5:46 ` Dan Nicolaescu
2015-12-15 16:05 ` Eli Zaretskii
2015-12-15 16:37 ` Eric Hanchrow
2015-12-15 16:40 ` Eli Zaretskii
2015-12-18 4:59 ` Dan Nicolaescu
2020-09-05 14:50 ` Lars Ingebrigtsen
2020-09-05 15:31 ` Eli Zaretskii
2015-12-14 6:35 ` Dan Nicolaescu
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=yxq37v5yofo.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=22154@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric.hanchrow@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.