Date: Tue, 12 Oct 2004 13:47:54 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: freebsd@amadeus.demon.nl Cc: freebsd-questions@freebsd.org Subject: Re: colourization in ls command Message-ID: <20041012104754.GA17947@orion.daedalusnetworks.priv> In-Reply-To: <3041E897-1C37-11D9-B5AA-0003939726F0@amadeus.demon.nl> References: <208449C5-1C32-11D9-B5AA-0003939726F0@amadeus.demon.nl> <20041012100113.GB17178@orion.daedalusnetworks.priv> <3041E897-1C37-11D9-B5AA-0003939726F0@amadeus.demon.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2004-10-12 12:12, FreeBSD questions mailing list <FreeBSD@amadeus.demon.nl> wrote: >On 12 okt 2004, at 12:01, Giorgos Keramidas wrote: >>On 2004-10-12 11:36, FreeBSD questions mailing list >><FreeBSD@amadeus.demon.nl> wrote: >>>hello, >>>why is the colouization lost in: >>>ls -alhG | more >> >>Because you piped the output to more(1). > > hmm, of course... > is there a way to preserve it and still have it display page after page? I'm not sure. I very rarely use colors myself and, as a result of this, have not researched this at all. I just happened to know that more(1) does this trick, because I regularly use it on Gentoo Linux installations to strip off the colors from the output of commands like emerge(1), which stupidly insist printing colorful output even if I connect over SSH and set my TERM to vt220.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041012104754.GA17947>