From: Aleksey Midenkov <midenok@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Colors on TTY (v26)
Date: Sun, 31 Mar 2019 21:09:56 +0300 [thread overview]
Message-ID: <CAF8BazBVWrYKDnApJknVjA_xZgE=kq+wQnksTunzpPz_6zVQgA@mail.gmail.com> (raw)
In-Reply-To: <83pnq7gcw9.fsf@gnu.org>
On Sun, Mar 31, 2019 at 8:41 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Aleksey Midenkov <midenok@gmail.com>
> > Date: Sun, 31 Mar 2019 20:20:56 +0300
> > Cc: help-gnu-emacs@gnu.org
> >
> > Emacs doesn't hard-code terminal names, but it has Lisp libraries
> > under lisp/term/ which are loaded by the terminal name. If you have a
> > terminal that behaves like one of the ones known to Emacs, you need
> > only copy the relevant Lisp library under lisp/term/ to the name of
> > your terminal (with the .el extension), and things should work from
> > there.
> >
> > I tried different terminal names. It seems, that it understands "xterm-"
> prefix. The remaining part can be
> > arbitrary: I literally tried "xterm-something" and it worked. I guess,
> there is no such file "xterm-something" in the
> > library. In any case, it's much better to rename terminal to "xterm-*",
> than deal with distributed files.
>
> Just do "ls lisp/term/*.el" and see what you've got there.
>
And?
>
> > The full color list is indeed set during startup, so if you invoke
> > list-colors-display too early during startup, you will not see that.
> > This is not a bug, as Emacs can not know the color capabilities of the
> > terminal until it probes them.
> >
> > This is indeed a bug: different result returned by same routine. Either
> list-colors-display should not exist at an
> > early stage or color capability probe should be done earlier.
>
> What do you mean "should not exists"? The code is there, it uses
> whatever knowledge it has when you call it. Where you did call it, it
> didn't yet query the terminal to see how many colors it supports, and
> didn't set up their names. IOW, you are shooting yourself in the foot
> by calling the function too early. There are various hooks provided
> by startup.el which allow you to call this function when colors are
> set up; do that, and Bob's your uncle.
>
>
You may call it anything you like, but this misleading behavior causes
trouble.
--
All the best,
Aleksey Midenkov
@midenok
next prev parent reply other threads:[~2019-03-31 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 8:22 Colors on TTY (v26) Aleksey Midenkov
2019-03-31 15:15 ` Eli Zaretskii
2019-03-31 17:20 ` Aleksey Midenkov
2019-03-31 17:41 ` Eli Zaretskii
2019-03-31 18:09 ` Aleksey Midenkov [this message]
2019-03-31 18:26 ` Eli Zaretskii
2019-03-31 19:45 ` Aleksey Midenkov
2019-03-31 20:51 ` Stefan Monnier
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='CAF8BazBVWrYKDnApJknVjA_xZgE=kq+wQnksTunzpPz_6zVQgA@mail.gmail.com' \
--to=midenok@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.