From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eric Hanchrow Newsgroups: gmane.emacs.bugs Subject: bug#22154: 25.0.50; emacsclient -c "breaks" 256-color display in server Date: Sun, 13 Dec 2015 18:47:32 +0000 Message-ID: References: <8361025k9u.fsf@gnu.org> <83si3643iw.fsf@gnu.org> <83poya42l5.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1140cd06cd51e00526cbfd3e X-Trace: ger.gmane.org 1450032510 10974 80.91.229.3 (13 Dec 2015 18:48:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Dec 2015 18:48:30 +0000 (UTC) Cc: 22154@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Dec 13 19:48:16 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a8Bgu-00011q-6K for geb-bug-gnu-emacs@m.gmane.org; Sun, 13 Dec 2015 19:48:16 +0100 Original-Received: from localhost ([::1]:56253 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8Bgo-0004FA-AJ for geb-bug-gnu-emacs@m.gmane.org; Sun, 13 Dec 2015 13:48:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56986) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8Bgj-0004EJ-Nv for bug-gnu-emacs@gnu.org; Sun, 13 Dec 2015 13:48:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a8Bgg-0003yh-Eo for bug-gnu-emacs@gnu.org; Sun, 13 Dec 2015 13:48:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:42893) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8Bgg-0003yb-B8 for bug-gnu-emacs@gnu.org; Sun, 13 Dec 2015 13:48:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1a8Bgg-0004Z4-0g for bug-gnu-emacs@gnu.org; Sun, 13 Dec 2015 13:48:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eric Hanchrow Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 13 Dec 2015 18:48:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22154 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22154-submit@debbugs.gnu.org id=B22154.145003246917524 (code B ref 22154); Sun, 13 Dec 2015 18:48:01 +0000 Original-Received: (at 22154) by debbugs.gnu.org; 13 Dec 2015 18:47:49 +0000 Original-Received: from localhost ([127.0.0.1]:50495 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1a8BgT-0004YZ-5u for submit@debbugs.gnu.org; Sun, 13 Dec 2015 13:47:49 -0500 Original-Received: from mail-io0-f170.google.com ([209.85.223.170]:33416) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1a8BgR-0004YN-FT for 22154@debbugs.gnu.org; Sun, 13 Dec 2015 13:47:47 -0500 Original-Received: by iow186 with SMTP id 186so5380661iow.0 for <22154@debbugs.gnu.org>; Sun, 13 Dec 2015 10:47:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=mrB+vgqm4MiCqTjk5w92faaAzOfrH3/29/dk/vvXaH4=; b=lOpxr6HOyRNGwqgNoD21uoN4PERcG2unScwJElaD3ouKrgaJHPlTDI4RHU4Sc//vKZ SV1aVAPSLedFi7fnKJw0x5DykBZCuSIAhWj4g33Pm6806JygMtkyZ8qzQA9mZTzVUrri oi6az1ZO2X1Mltidt6I0YwgNVzM2WkCjoDg0CY+3//wgntxGptdFQsT1PkEEQEWL0LzN lPb7zn8h5oLD/ZVoLhr3UQfFtUKrDLxYtyZO6EjqloYMzOFdQ8JqQBQK0IpdEM7y2DgH h6ZAc8zWQfkWzISlN6rSkjrJBMwsR7mu+/dLx3w764Gr62kjwQBFt2LuSeV12DTpXCOZ 69Sw== X-Received: by 10.107.32.209 with SMTP id g200mr23640921iog.39.1450032461858; Sun, 13 Dec 2015 10:47:41 -0800 (PST) In-Reply-To: <83poya42l5.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:109951 Archived-At: --001a1140cd06cd51e00526cbfd3e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I assume you meant `tty-color-mode-alist'. After running `emacs -Q' with TERM set to `xterm-256color`, I see tty-color-mode-alist is a variable defined in =E2=80=98tty-colors.el=E2=80= =99. Its value is ((never . -1) (no . -1) (default . 0) (auto . 0) (ansi8 . 8) (always . 8) (yes . 8)) After the client frame is created, it's the same. `terminal-init-xterm` does indeed run when I create the client frame, but as you can see, it doesn't modify tty-color-mode-alist. On Sun, Dec 13, 2015 at 10:37 AM Eli Zaretskii wrote: > > Date: Sun, 13 Dec 2015 20:17:11 +0200 > > From: Eli Zaretskii > > Cc: 22154@debbugs.gnu.org > > > > > From: Eric Hanchrow > > > Date: Sun, 13 Dec 2015 10:05:20 -0800 > > > Cc: 22154@debbugs.gnu.org > > > > > > Does the patch below fix the problem? > > > > > > It doesn't seem to make any difference. > > > > Strange, it did make a difference on my system. > > > > I guess I will then have to ask you to step in a debugger through > > set_tty_color_mode and tty_setup_colors, and tell what is stored in > > the default_* members of the tty object during the main Emacs > > initialization and when the client frame is created. I have no access > > to a system with a 256-color xterm. > > It could also be tty-color-alist. Can you tell me what's in it after > Emacs starts on a 256-color xterm, and after the client frame is > created? Also, does xterm.el initialization get called for the client > frame, and does it modify tty-color-alist? > > --001a1140cd06cd51e00526cbfd3e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I assume you meant `tty-color-mode-alist'.=C2=A0 After= running `emacs -Q' with TERM set to `xterm-256color`, I see

tty-color-mode-alist is a variable defined in =E2=80=98tty-co= lors.el=E2=80=99.
Its value is ((never . -1)
=C2=A0(no = . -1)
=C2=A0(default . 0)
=C2=A0(auto . 0)
= =C2=A0(ansi8 . 8)
=C2=A0(always . 8)
=C2=A0(yes . 8))

After the client frame is created, it's t= he same.

`terminal-init-xterm` does indeed run whe= n I create the client frame, but as you can see, it doesn't modify tty-= color-mode-alist.


On Sun, Dec 13, 2015 at 10:37 AM Eli Zaretskii <eliz@gnu.org> wrote:
> Date: Sun, 13 Dec 2015 20:17:11 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 22154@d= ebbugs.gnu.org
>
> > From: Eric Hanchrow <eric.hanchrow@gmail.com>
> > Date: Sun, 13 Dec 2015 10:05:20 -0800
> > Cc: 22= 154@debbugs.gnu.org
> >
> >=C2=A0 =C2=A0 =C2=A0Does the patch below fix the problem?
> >
> > It doesn't seem to make any difference.
>
> Strange, it did make a difference on my system.
>
> I guess I will then have to ask you to step in a debugger through
> set_tty_color_mode and tty_setup_colors, and tell what is stored in > the default_* members of the tty object during the main Emacs
> initialization and when the client frame is created.=C2=A0 I have no a= ccess
> to a system with a 256-color xterm.

It could also be tty-color-alist.=C2=A0 Can you tell me what's in it af= ter
Emacs starts on a 256-color xterm, and after the client frame is
created?=C2=A0 Also, does xterm.el initialization get called for the client=
frame, and does it modify tty-color-alist?

--001a1140cd06cd51e00526cbfd3e--