better support for color ls on 256 color terminals

2007-09-21 Thread Dan Nicolaescu
Modern terminals support 256 colors. It would be great if ls --color could take advantage of the higher number of colors to improve the way things are displayed. The 256 available colors can be seen by running the 256color2.pl script that comes with xterm, or by running env TERM=xterm-256color

ls: write error: Broken pipe

2007-11-01 Thread Dan Nicolaescu
I have been using this alias: lt = 'ls -lt | head' for a long long time, on many systems. On Fedora 7 I get this from time to time: cd /usr/lib lt total 162508 drwxr-xr-x 10 rpm rpm 4096 2007-10-31 00:11 rpm/ drwxr-xr-x 13 root root 4096 2007-10-31 00:11 firefox-2.0.0.5/

Re: ls: write error: Broken pipe

2007-11-02 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: I have been using this alias: lt = 'ls -lt | head' ... ls: write error: Broken pipe Is there any reason for this error to be printed? Hi Dan, You should see it only if you have

Re: ls: write error: Broken pipe

2007-11-02 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: I have been using this alias: lt = 'ls -lt | head' ... ls: write error: Broken pipe

Re: ls: write error: Broken pipe

2007-11-08 Thread Dan Nicolaescu
Paul Eggert [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] writes: Nope, nothing. Can you determine whether processes have SIGPIPE trapped somehow? If so, that's the problem; and you can try to track that down. For example, what does this shell command do

Re: ls: write error: Broken pipe

2007-11-08 Thread Dan Nicolaescu
[EMAIL PROTECTED] (Bob Proulx) writes: Dan Nicolaescu wrote: Paul Eggert writes: bash -c '(while echo foo; do :; done); echo status=$? 2' | head If it eventually outputs write error: Broken pipe, you have SIGPIPE trapped, and that would explain your problem

Re: ls: write error: Broken pipe

2007-11-09 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] (Bob Proulx) writes: Dan Nicolaescu wrote: Paul Eggert writes: bash -c '(while echo foo; do :; done); echo status=$? 2' | head

Re: ls: write error: Broken pipe

2007-11-09 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] (Bob Proulx) writes: Dan Nicolaescu wrote: Paul

Re: ls: write error: Broken pipe

2007-11-09 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Jim Meyering [EMAIL PROTECTED] wrote: Dan Nicolaescu [EMAIL PROTECTED] wrote: ... Have you tried changing your login shell to bash? Yeah, changing the login shell to bash works. But so does running bash from tcsh and running

Re: ls: write error: Broken pipe

2007-11-09 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: ... I created a new account with /bin/tcsh as a shell, deleted all the dot files in that new account, logged in on a linux console and run the perl command above. It prints IGNORE. tcsh

Re: ls: write error: Broken pipe

2007-11-11 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: ... I created a new account with /bin/tcsh as a shell, deleted all the dot files in that new

Re: ls: write error: Broken pipe

2007-11-18 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: ... I created a new account with /bin/tcsh as a shell, deleted all the dot files in that new

Re: ls: write error: Broken pipe

2007-11-19 Thread Dan Nicolaescu
Jim Meyering [EMAIL PROTECTED] writes: Dan Nicolaescu [EMAIL PROTECTED] wrote: ... I have installed Fedora 8 on another 32bit x86 system, and the problem appears there too. (I moved /etc/csh* out of the way, used a freshly created account that uses /bin/tcsh. I also