unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Rami Ylimäki" <rami.ylimaki@vincit.fi>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30917@debbugs.gnu.org, Oliver Laslett <oliver@cytora.com>
Subject: bug#30917: 26.0.91; True color emacs in termite
Date: Wed, 28 Mar 2018 01:21:03 +0300	[thread overview]
Message-ID: <CAHmfpf_iMnsDjhGkU331k9b+rOj_Mry7t16VocK_X8qY4uQtzA@mail.gmail.com> (raw)
In-Reply-To: <83fu4mg977.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]

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=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.

[-- Attachment #2: Type: text/html, Size: 2582 bytes --]

      reply	other threads:[~2018-03-27 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 10:30 bug#30917: 26.0.91; True color emacs in termite Oliver Laslett
2018-03-23 19:04 ` Eli Zaretskii
2018-03-23 19:51   ` Oliver Laslett
2018-03-24  0:19     ` Rami Ylimäki
2018-03-26 10:12       ` Oliver Laslett
2018-03-26 15:14         ` Eli Zaretskii
2018-03-27 22:21           ` Rami Ylimäki [this message]

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=CAHmfpf_iMnsDjhGkU331k9b+rOj_Mry7t16VocK_X8qY4uQtzA@mail.gmail.com \
    --to=rami.ylimaki@vincit.fi \
    --cc=30917@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=oliver@cytora.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).