all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bois Francois-Xavier <fxbois@gmail.com>, emacs-devel@gnu.org
Subject: Re: emacs, true color and iterm2
Date: Mon, 09 Sep 2013 19:12:30 -0400	[thread overview]
Message-ID: <jwv61u9zj2v.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83li35kbuz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Sep 2013 22:56:36 +0300")

>> iterm2, a widely used open source terminal on OSX, is working on offering
>> compatibility with true color (3-byte color mode).
>> It can be a great feature for emacs users working on terminals.
>> An interesting discussion about the best way to "code" the colors is taking
>> place on https://code.google.com/p/iterm2/issues/detail?id=218.
>> Could a core emacs developer give them some feedbacks ? (does emacs
>> requires a special encoding ?)

> What Emacs needs can be seen from its support of xterm-256, see
> xterm.el in the Emacs distribution.  In a nutshell, someone should
> write a function that registers all the supported colors as
> xterm-register-default-colors does.

Tho, obviously, for 2bit color support, we won't will want to have
support for tty colors without going through some approximation table.


        Stefan



  reply	other threads:[~2013-09-09 23:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 17:54 emacs, true color and iterm2 Bois Francois-Xavier
2013-09-09 19:56 ` Eli Zaretskii
2013-09-09 23:12   ` Stefan Monnier [this message]
2013-09-10  2:07     ` Stefan Monnier
2013-09-10  2:51       ` Eli Zaretskii
2013-09-10 14:57         ` Stefan Monnier
2013-09-10 15:15           ` Eli Zaretskii
2013-09-10  2:49     ` Eli Zaretskii
2013-09-10 10:56 ` Richard Stallman
2013-09-10 11:26   ` Bois Francois-Xavier
2013-09-10 14:43     ` Andreas Schwab
2013-09-10 20:36     ` Richard Stallman

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=jwv61u9zj2v.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fxbois@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 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.