From: Yuan Luo <yuan.hypnos.luo@gmail.com>
To: Peter Dyballa <Peter_Dyballa@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: customizing dircolors doesn't take effect in emacs shell
Date: Sun, 15 Jan 2012 17:34:35 -0500 [thread overview]
Message-ID: <CAMY509mebVt+HvC+X_+5Hzyp_bySOP8=uk_sYdYX3fHvXA17Hg@mail.gmail.com> (raw)
In-Reply-To: <14CA6C8F-B82D-4FD4-B6E9-4344B31B5E2F@web.de>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
I found the solution:
adding a line TERM=dumb in the ~/.dircolors file did the trick, as emacs
inferior mode shell type is dumb.
Thanks for all the help getting me close to the answer!
Best,
Yuan
On Mon, Jan 9, 2012 at 3:56 PM, Peter Dyballa <Peter_Dyballa@web.de> wrote:
>
> Am 9.1.2012 um 17:43 schrieb Yuan Luo:
>
> > All aliases in ~/.bashrc are listed in emacs shells.
> > I already had have ansi-color-for-comint-mode-on set.
> > execution of ls traces to /bin/ls
>
> Does it work when you use
>
> /bin/ls --color=auto /bin
> /bin/ls --color /bin
>
> manually and directly?
>
> My manual page explains:
>
> With --color=auto, ls emits color codes only when standard output
> is connected to a terminal. The LS_COLORS environment variable can change
> the settings. Use the dircolors command to set it.
>
> There is a chance that LS_COLORS hinders ls, it's also possible that in
> *shell* buffer standard output is not connected to a terminal. The latter
> seems to be true for me on Mac OS X (10.6.8, Snow Leopard). So by omitting
> the "=auto" should make your aliases work.
>
> --
> Greetings
>
> Pete
>
> Bake pizza not war!
>
>
[-- Attachment #2: Type: text/html, Size: 1597 bytes --]
prev parent reply other threads:[~2012-01-15 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 21:28 customizing dircolors doesn't take effect in emacs shell Yuan Luo
2012-01-08 0:12 ` Peter Dyballa
2012-01-08 0:36 ` Yuan Luo
2012-01-08 10:50 ` Peter Dyballa
2012-01-09 1:05 ` Yuan Luo
2012-01-09 9:53 ` Peter Dyballa
2012-01-09 16:43 ` Yuan Luo
2012-01-09 16:48 ` Yuan Luo
2012-01-09 20:56 ` Peter Dyballa
2012-01-15 22:34 ` Yuan Luo [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
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='CAMY509mebVt+HvC+X_+5Hzyp_bySOP8=uk_sYdYX3fHvXA17Hg@mail.gmail.com' \
--to=yuan.hypnos.luo@gmail.com \
--cc=Peter_Dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
/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).