On Tue, Jul 04, 2000 at 04:17:53PM -0700, Doug Barton wrote:
>
> So, I've put my time where my mouth is and produced the attached patch
> for ls.1. I am 100% open to modifications of both style and content, my
> only request being that someone commit _something_ before 4.1 goes out
> the do
John Baldwin wrote:
>
> On 04-Jul-00 Doug Barton wrote:
> > John Baldwin wrote:
> >
> >> >> XTerm*termName: xterm-color
> >> >
> >> > Ok, that's a good solution, I was just using .bashrc. My point is not
> >> > so much why, but that it be properly documented. Do you want to handle
> >> > th
Hmm.. how about adding this XTerm*termname: xterm-color stuff to a default
Xresources file in /usr/share/skel/, or to some default Xresources file
in the X directory tree itself? (I haven't messed with X resources too
much, guess it shows ;)
This would break xterms running on monochrome monitors
On 04-Jul-00 Doug Barton wrote:
> John Baldwin wrote:
>
>> >> XTerm*termName: xterm-color
>> >
>> > Ok, that's a good solution, I was just using .bashrc. My point is not
>> > so much why, but that it be properly documented. Do you want to handle
>> > the update of the ls man page, or do yo
John Baldwin wrote:
> >> XTerm*termName: xterm-color
> >
> > Ok, that's a good solution, I was just using .bashrc. My point is not
> > so much why, but that it be properly documented. Do you want to handle
> > the update of the ls man page, or do you want me to PR a patch?
>
> Umm, honestl
On 04-Jul-00 Sean Lutner wrote:
> Well, I'm not really using xterm, I use Eterms, and I've NEVER had this
> problem before, so it was non-obvious to me. I know the Eterms I'm using
> are capable of displaying color ls output, because it does so when logged
> into shells. Also, I'm not sure if thi
On Mon, 3 Jul 2000, John Baldwin wrote:
>
> On 03-Jul-00 Doug Barton wrote:
> > Brian Fundakowski Feldman wrote:
> >>
> >> On Sun, 2 Jul 2000, Sean Lutner wrote:
> >>
> >> > I'm experiencing the same thing. ls --color doesn't seem to work for me
> >> > unless like Doug, I set TERM=xterm-colo
On 03-Jul-00 Doug Barton wrote:
> Brian Fundakowski Feldman wrote:
>>
>> On Sun, 2 Jul 2000, Sean Lutner wrote:
>>
>> > I'm experiencing the same thing. ls --color doesn't seem to work for me
>> > unless like Doug, I set TERM=xterm-color.
>>
>> That's because the "color" escape sequences are d
On Mon, Jul 03, 2000 at 12:10:13AM -0700, Doug Barton wrote:
> Brian Fundakowski Feldman wrote:
>
> > That's because the "color" escape sequences are defined for xterm-color
> > in termcap; xterm-color is defined as a superset of xterm (see the tc=
> > directive).
>
> Right... I am down w
Brian Fundakowski Feldman wrote:
>
> On Sun, 2 Jul 2000, Sean Lutner wrote:
>
> > I'm experiencing the same thing. ls --color doesn't seem to work for me
> > unless like Doug, I set TERM=xterm-color.
>
> That's because the "color" escape sequences are defined for xterm-color
> in termcap; xterm
On Sun, 2 Jul 2000, Sean Lutner wrote:
> I'm experiencing the same thing. ls --color doesn't seem to work for me
> unless like Doug, I set TERM=xterm-color.
That's because the "color" escape sequences are defined for xterm-color
in termcap; xterm-color is defined as a superset of xterm (see the
I'm experiencing the same thing. ls --color doesn't seem to work for me
unless like Doug, I set TERM=xterm-color.
On Sun, 2 Jul 2000, Doug Barton wrote:
> The new improved ncurses version of the color ls stuff doesn't display
> for me if I am in a "normal" xterm. If I set TERM equal to xte
The new improved ncurses version of the color ls stuff doesn't display
for me if I am in a "normal" xterm. If I set TERM equal to xterm-color
I'm back in business. Is this expected behavior? If so, a note to that
effect in the man page would help reduce user confusion. I'll be happy
to sub
13 matches
Mail list logo
