From: "Sergei" <sergio.pokrovskij@gmail.com>
Subject: Re: help with M-x term
Date: 18 Jul 2006 00:01:31 -0700 [thread overview]
Message-ID: <1153206091.868784.104930@p79g2000cwp.googlegroups.com> (raw)
In-Reply-To: <873bd3yane.fsf@tiger.rapttech.com.au>
Tim X wrote:
[...]
> Yes, I've seen solutions of this style before. Its certainly one
> solution. In fact, under Debian, the default .bashrc has
> # enable color support of ls and also add handy aliases
> if [ "$TERM" != "dumb" ]; then
> eval `dircolors -b`
> alias ls='ls --color=auto'
> alias dir='ls --color=auto --format=vertical'
> alias vdir='ls --color=auto --format=longx
> fi
> Which means ls colours are not used within M-x shell as it sets TERM
> to dumb. This approach is I think more general in that it will
> prevent ls colours from being used in any dumb terminal, not just
> emacs' shell.
Maybe that's true. But actually there are more colored thing than the
directories.
So far I was unable to solve the color problem with the perl debugger
:(
> I also note you are using the variable $OSVAR to detect if running
> under Linux, but I don't think this is a "standard' variable
> (i.e. it is distribution/local/user specific). I only mention it in
> case someone uses your code snippet and is wondering why colour ls
> is not behaving as expected.
You are right, I set OSVAR myself on the basis of uname inquiry.
--
Sergei
next prev parent reply other threads:[~2006-07-18 7:01 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
2006-07-14 10:35 ` Sergei
2006-07-15 0:28 ` Tim X
2006-07-18 7:01 ` Sergei [this message]
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=1153206091.868784.104930@p79g2000cwp.googlegroups.com \
--to=sergio.pokrovskij@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.
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).