all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: Matthew Carter <m@ahungry.com>
Cc: emacs-devel@gnu.org
Subject: Re: Can we support apt's funky ANSI escapes?
Date: Fri, 22 Jul 2016 17:59:03 -0400	[thread overview]
Message-ID: <62a819db-8e39-ba88-d7e7-f6b7ce46cd98@gmail.com> (raw)
In-Reply-To: <87r3alxujl.fsf@ahungry.com>


[-- Attachment #1.1: Type: text/plain, Size: 909 bytes --]

On 2016-07-22 16:54, Matthew Carter wrote:
> Clément Pit--Claudel <clement.pit@gmail.com> writes:
> 
>> On 2016-07-20 13:05, Robert Weiner wrote:
>>> What happens if you use {M-x ansi-term RET}?
>>
>> I guess it would work fine, but I'd rather not use ansi-term, if possible.
>>
> 
> The ansi-color package has a function, #'ansi-color-apply-on-region
> which works well for translating these to colorized font faces (I use it
> on some shell output from my own custom functions that include these
> escape codes).

Hmm, I'm not sure I understand. shell-mode already translates most ANSI escapes to colorized faces, doesn't it?
For example, in emacs -Q, running M-x shell and typing `env TERM=xterm ls --color' gives me properly colored output.

AFAICT, the only thing that's missing is support for the two specific codes (61 and 62) that `apt' is using. Isn't that right?

Clément.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-07-22 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 14:52 Can we support apt's funky ANSI escapes? Clément Pit--Claudel
2016-07-20 16:33 ` Stefan Monnier
2016-07-20 17:05 ` Robert Weiner
2016-07-20 19:38   ` Clément Pit--Claudel
2016-07-22 20:54     ` Matthew Carter
2016-07-22 21:59       ` Clément Pit--Claudel [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62a819db-8e39-ba88-d7e7-f6b7ce46cd98@gmail.com \
    --to=clement.pit@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=m@ahungry.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.