From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Rami =?UTF-8?Q?Ylim=C3=A4ki?= Newsgroups: gmane.emacs.bugs Subject: bug#30917: 26.0.91; True color emacs in termite Date: Wed, 28 Mar 2018 01:21:03 +0300 Message-ID: References: <83woy2haud.fsf@gnu.org> <83fu4mg977.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000005a10ba05686c4e6d" X-Trace: blaine.gmane.org 1522189213 23401 195.159.176.226 (27 Mar 2018 22:20:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 27 Mar 2018 22:20:13 +0000 (UTC) Cc: 30917@debbugs.gnu.org, Oliver Laslett To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Mar 28 00:20:09 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f0wwq-0005wk-Ry for geb-bug-gnu-emacs@m.gmane.org; Wed, 28 Mar 2018 00:20:09 +0200 Original-Received: from localhost ([::1]:36363 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0wys-00015F-Db for geb-bug-gnu-emacs@m.gmane.org; Tue, 27 Mar 2018 18:22:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56808) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0wyj-00013k-73 for bug-gnu-emacs@gnu.org; Tue, 27 Mar 2018 18:22:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f0wyg-00025F-0G for bug-gnu-emacs@gnu.org; Tue, 27 Mar 2018 18:22:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:48452) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f0wyf-00025B-Sb for bug-gnu-emacs@gnu.org; Tue, 27 Mar 2018 18:22:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f0wyf-00064A-MF for bug-gnu-emacs@gnu.org; Tue, 27 Mar 2018 18:22:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Rami =?UTF-8?Q?Ylim=C3=A4ki?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 27 Mar 2018 22:22:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30917 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30917-submit@debbugs.gnu.org id=B30917.152218927123258 (code B ref 30917); Tue, 27 Mar 2018 22:22:01 +0000 Original-Received: (at 30917) by debbugs.gnu.org; 27 Mar 2018 22:21:11 +0000 Original-Received: from localhost ([127.0.0.1]:56349 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f0wxr-000634-AS for submit@debbugs.gnu.org; Tue, 27 Mar 2018 18:21:11 -0400 Original-Received: from mail-ot0-f181.google.com ([74.125.82.181]:39089) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f0wxp-00062q-MD for 30917@debbugs.gnu.org; Tue, 27 Mar 2018 18:21:10 -0400 Original-Received: by mail-ot0-f181.google.com with SMTP id h8-v6so527330oti.6 for <30917@debbugs.gnu.org>; Tue, 27 Mar 2018 15:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vincit.fi; s=ticniv; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VaETcMw6awjpNANTXH3+puMhRrYrds1TPbGQPChZ0rU=; b=caCz0ZoR/OdC5AZFmr3Ki6waigczAOFb9SJwAO0tIkTC1atBjSmEcrumAmHU/Zizov ZMRTq6jJn8qGR+Ul3SEo24KiFAQW8FsxOPV4/50YgvpKgcY8dvTELq9iyt1zfLM0zJJM LD5nN1dgewk5Fk3GYDwHcAiEspv8WiZb9OUpM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VaETcMw6awjpNANTXH3+puMhRrYrds1TPbGQPChZ0rU=; b=J6F6gF//pfa/qeP5p0JaJFOVxmIpOnGkgaEOOXg+jLRqv9uE683igCkaOr542ZB47q UKSBHMTAnWxgqGWHQTizLIm0rfSdjltHvupIcGeJ2UGIejAEY+s3Jd98j5mJzyzpPC9N 8BpaN16H+EXA/mkaetdP0vywhCGklJVvsBwoAYTBNqWNAwoY/CPekTfPJ7E4cbaDSQDV hRMj5+6rpFY66FbPTxo6WfrujDJgDm3rj9dLb63NMUvUIjvMjyIsxEwye4DG90wUZDUI XWEz7yY61hEiRfBTNvAhDpvRxC37PH4MjnS/+mo9N6oEZKrge9tNcMLbMTSPXOkxa06d zxJg== X-Gm-Message-State: AElRT7EmhbyYMlnsL9nK26w2MsQoFW7TkzsY+obXzg3hu+ONyLmKk84H 9oAG2lXdNcdY8iCGfxMjtnE2HUEAjupCD2ybqxK9PA== X-Google-Smtp-Source: AIpwx4+wo0TcBDKR2KTPsEFIbqjjGg1Hemfxou/HSi8eFH7zZKDbjyBUCp8quyu1WbuxbqHyCJOJaAzcoCjycCTmaj8= X-Received: by 2002:a9d:305a:: with SMTP id w26-v6mr701829otd.292.1522189263829; Tue, 27 Mar 2018 15:21:03 -0700 (PDT) Original-Received: by 10.201.30.198 with HTTP; Tue, 27 Mar 2018 15:21:03 -0700 (PDT) In-Reply-To: <83fu4mg977.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" Xref: news.gmane.org gmane.emacs.bugs:144662 Archived-At: --0000000000005a10ba05686c4e6d Content-Type: text/plain; charset="UTF-8" 2018-03-26 18:14 GMT+03:00 Eli Zaretskii : > > From: Oliver Laslett > > Date: Mon, 26 Mar 2018 11:12:45 +0100 > > Cc: Eli Zaretskii , 30917@debbugs.gnu.org > > > > Rami, using TERM=xterm-direct2 worked! I tried many other options > without success. Many thanks, it seems > > that I have true colours. The only difference is that when I exit and > return to the terminal, my prompt appears > > at the bottom and emacs remains in the terminal buffer (i.e. i have to > call $ clear to clear the terminal buffer). I > > have tested and this is also happens with any command (e.g. `less`) so I > guess related to using > > TERM=xterm-direct2 and not emacs related. > > Rami, do you think this warrants addition of a few words to the FAQ? > Eli, I don't think we should go too much into the details of different TERM specs in the Emacs FAQ. Version 26 FAQ explains how to use a custom TERM spec. Version 27 FAQ also explains how to list the standard TERM specs so that the user can choose one for their terminal. That should be enough. Of course we could apply the version 27 FAQ changes to version 26 as well. In this particular case, xterm-direct2 happens to define the [rs]mcup capabilities in a different manner from other TERMs, which causes the screen contents to be restored incorrectly in many terminals. However, I wouldn't worry about this since use of xterm-direct2 seems to be deprecated according to Terminfo sources. Oliver, if you follow the instructions in version 27 FAQ ( http://git.savannah.gnu.org/cgit/emacs.git/tree/doc/misc/efaq.texi, search for xterm-direct), you'll see how to list different direct mode terminals on your computer. Choosing vte-direct for a vte-compatible terminal could be one option to avoid the incorrectly restored screen. --0000000000005a10ba05686c4e6d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018= -03-26 18:14 GMT+03:00 Eli Zaretskii <eliz@gnu.org>:
> From: Oliver Laslett <oliver@cytora.com>
> Date: Mon, 26 Mar 2018 11:12:45 +0100
> Cc: Eli Zaretskii <eliz@gnu.org= >, 30917@debbugs.gnu.org >
> Rami, using TERM=3Dxterm-direct2 worked! I tried many other options wi= thout success. Many thanks, it seems
> that I have true colours. The only difference is that when I exit and = return to the terminal, my prompt appears
> at the bottom and emacs remains in the terminal buffer (i.e. i have to= call $ clear to clear the terminal buffer). I
> have tested and this is also happens with any command (e.g. `less`) so= I guess related to using
> TERM=3Dxterm-direct2 and not emacs related.

Rami, do you think this warrants addition of a few words to the FAQ?

Eli, I don't th= ink we should go too much into the details of different TERM specs in the E= macs FAQ. Version 26 FAQ explains how to use a custom TERM spec. Version 27= FAQ also explains how to list the standard TERM specs so that the user can= choose one for their terminal. That should be enough. Of course we could a= pply the version 27 FAQ changes to version 26 as well.

In this particular case, x= term-direct2 happens to define the [rs]mcup capabilities in a different man= ner from other TERMs, which causes the screen contents to be restored incor= rectly in many terminals. However, I wouldn't worry about this since us= e of xterm-direct2 seems to be deprecated according to Terminfo sources.

Oliver, = if you follow the instructions in version 27 FAQ (http://git.savannah.g= nu.org/cgit/emacs.git/tree/doc/misc/efaq.texi, search for xterm-direct)= , you'll see how to list different direct mode terminals on your comput= er. Choosing vte-direct for a vte-compatible terminal could be one option t= o avoid the incorrectly restored screen.
--0000000000005a10ba05686c4e6d--