unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
Subject: Re: help with M-x term
Date: Fri, 14 Jul 2006 15:25:54 +1000	[thread overview]
Message-ID: <877j2gycyl.fsf@tiger.rapttech.com.au> (raw)
In-Reply-To: mailman.4055.1152797235.9609.help-gnu-emacs@gnu.org

op132650c@mail.telepac.pt writes:

>>   Is there some reason why you aren't using M-x shell?
>
> I don't want to detour the attention about the question of William Daffer, but i
> also prefer M-x term instead of M-x shell, because the output of M-x shell is
> not well formatted compared to M-x term.
>
> Now i put the following question:
>
> What's the difference between M-x shell and M-x term?
>
> How can i configure M-x shell to be well formatted?
>
> One example of the bad formatation of the output of M-x shell, is when i do ls
> -la.
> I get the following:
>
> ]]] file1     ]]] file3^]]]     ]]] file5^]]]
>  ]]] file2   ]]] file4^]]]     ]]] file6^]]]
>
>
> With the M-x term i get well formatted:
>
> file1   file3   file5
> file2   file4   file6
>

The difference in 'formatting' you have observed is because M-x shell
doesn't understand ANSI escape codes for colour. When you use the ls
command and have it configured to display the output using different
colours for different file types, it does this by using andsi colour
escape sequences. However, M-x shell does not understand these "out of
the box". 

There are at least two solutions -

1. configure ls not to use escape sequences when displaying a
   directory listing in a dumb terminal - one of the ls --color=
   values should do this

2. Enable support for ansi colours in comint derived modes - do an
   apropos for ansi color. M-x shell will then be able to interpret
   the ansi colour codes.

3. Use M-x term

Tim



-- 
tcross (at) rapttech dot com dot au

  parent reply	other threads:[~2006-07-14  5:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 20:02 help with M-x term yz7502
2006-07-13  2:56 ` William Daffer
2006-07-13 13:27   ` op132650c
2006-07-13 14:03   ` yz7502
2006-07-13 15:10     ` William Daffer
2006-07-13 16:17       ` yz7502
     [not found]   ` <mailman.4055.1152797235.9609.help-gnu-emacs@gnu.org>
2006-07-13 15:16     ` William Daffer
2006-07-14  5:25     ` Tim X [this message]
2006-07-14 10:35       ` Sergei
2006-07-15  0:28         ` Tim X
2006-07-18  7:01           ` Sergei
2006-07-18  8:34             ` Tim X
2006-07-13 15:14 ` Kevin Rodgers

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=877j2gycyl.fsf@tiger.rapttech.com.au \
    --to=timx@nospam.dev.null \
    /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.
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).