all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: m-guelker@phoenixmail.de, 34224@debbugs.gnu.org
Subject: bug#34224: 25.1; ansi-term displays garbage on tree(1) command
Date: Tue, 29 Jan 2019 18:17:00 +0200	[thread overview]
Message-ID: <83imy730cj.fsf@gnu.org> (raw)
In-Reply-To: <4734c77f267638c51f581a8587948513@webmail.orcon.net.nz> (message from Phil Sainty on Tue, 29 Jan 2019 10:10:54 +1300)

severity 34224 wishlist
thanks

> Date: Tue, 29 Jan 2019 10:10:54 +1300
> From: Phil Sainty <psainty@orcon.net.nz>
> Cc: Marvin Gülker <m-guelker@phoenixmail.de>,
>  34224@debbugs.gnu.org
> 
> On 2019-01-29 04:47, Eli Zaretskii wrote:
> > If someone can tell what does 'tree' do to "turn on ANSI line graphics
> > hack", then perhaps we could decide whether there's something wrong
> > with how Emacs interprets the bytestream delivered to it by 'tree' in
> > this mode.
> 
> Does this help?
> 
> 
> $ tree -A | cat -v
> .
> ^[(0tqq ^[(Bbar
> ^[(0tqq ^[(Bfoo
> ^[(0mqq ^[(Bsubdir
> ^[(0    tqq ^[(Bbar
> ^[(0    mqq ^[(Bfoo
> 
> 1 directory, 4 files

Yes, thanks.  These are escape sequences which term.el doesn't
currently support:

  (defun term-emulate-terminal (proc str)
  [...]
		  ;; Ignore NUL, Shift Out, Shift In.
		  ((or ?\0 #xE #xF 'nil) nil))

Patches to add such support are welcome.





      reply	other threads:[~2019-01-29 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-27 18:09 bug#34224: 25.1; ansi-term displays garbage on tree(1) command Marvin Gülker
2019-01-28 11:03 ` Phil Sainty
2019-01-28 13:10   ` Marvin Gülker
2019-01-28 15:47     ` Eli Zaretskii
2019-01-28 21:10       ` Phil Sainty
2019-01-29 16:17         ` Eli Zaretskii [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=83imy730cj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34224@debbugs.gnu.org \
    --cc=m-guelker@phoenixmail.de \
    --cc=psainty@orcon.net.nz \
    /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.