From: Eli Zaretskii <eliz@gnu.org>
To: Eric Hanchrow <eric.hanchrow@gmail.com>
Cc: 22154@debbugs.gnu.org
Subject: bug#22154: 25.0.50; emacsclient -c "breaks" 256-color display in server
Date: Sun, 13 Dec 2015 22:49:44 +0200 [thread overview]
Message-ID: <83io423wgn.fsf@gnu.org> (raw)
In-Reply-To: <CAHZoxq93UQU+XobYxXzG1wpLt4xKwfPSprcnMcd_2GE9L-YCAA@mail.gmail.com> (message from Eric Hanchrow on Sun, 13 Dec 2015 12:26:10 -0800)
> From: Eric Hanchrow <eric.hanchrow@gmail.com>
> Date: Sun, 13 Dec 2015 12:26:10 -0800
> Cc: 22154@debbugs.gnu.org
>
> You can run the command ‘server-start’ with M-x ser-s RET
> terminal-init-xterm doin’ its thang. (tty-color-alist) returns a
> list of length 256.
> terminal-init-xterm is done. (tty-color-alist) now returns a list
> of length 8.
> When done with this frame, type C-x 5 0
>
> So clearly: xterm.el initialization _is_ getting called for the client
> frame, and it _does_ modify tty-color-alist.
Right. I guess we will have to make tty-defined-color-alist
terminal-specific, or something. This will have to wait until after
25.1, sorry.
next prev parent reply other threads:[~2015-12-13 20:49 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 [this message]
2015-12-14 6:21 ` Dan Nicolaescu
2015-12-14 15:56 ` Eli Zaretskii
2015-12-14 16:39 ` Dan Nicolaescu
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
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=83io423wgn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22154@debbugs.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 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).