> On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote:
>
> > Yes. Any program that expects colour to work.
>
> In what sense? The color codes are absorbed by xterm and it
> looks like it probably does without doing color stuff. Do you
> know of a program which actually has problems?
I
On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote:
>
> The more correct fix here is to stop worrying about fucking colourised ls
> output and focus on the seventeen dozen more important things that need
> your angst.
>
Hear hear. :) More important right now is sleep :)
Night night.
On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote:
> Yes. Any program that expects colour to work.
In what sense? The color codes are absorbed by xterm and it
looks like it probably does without doing color stuff. Do you
know of a program which actually has problems?
> The correct f
On Wed, Jul 19, 2000 at 01:17:26AM +0100, Josef Karthauser wrote:
> > That's not the issue.
>
> It is if my sun inherits the TERM from my FreeBSD box. That said
> it's the sun that's borked here, not us.
If we make the change that we are considering, then you will
set TERM=xterm on your FreeBS
> On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote:
>
> > joe@cuddy[503]: export TERM=xterm-color
> > joe@cuddy[504]: vi
> > xterm-color: Unknown terminal type
> > Visual needs addressable cursor or upline capability
> > :q
> > joe@cuddy[505]: uname -a
> > SunOS cuddy 5.6 Generic_
On Tue, Jul 18, 2000 at 05:11:41PM -0700, Matthew Hunt wrote:
> On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote:
>
> > joe@cuddy[503]: export TERM=xterm-color
> > joe@cuddy[504]: vi
> > xterm-color: Unknown terminal type
> > Visual needs addressable cursor or upline capability
>
FYI, I had a similar issue with dtterm coming into a FreeBSD box
from SCO UnixWare 7.
DTTERM does color, but the DTTERM /etc/termcap didn't work for
vim.
Adding the same lines to the dtterm termcap as for xterm-color fixed
it as well.
Larry
-- Start of PGP signed section.
> Matthew Hunt wro
On Tue, Jul 18, 2000 at 05:05:47PM -0700, Ron 'The InSaNe One' Rosson wrote:
> > I pretty sure that is the culprit. I know that on a sparc-netbsd machine I
> > login to on a regular basis doesn't have an xterm-color. And I've known
> > friends who've been bitten by this on other Unices. In the
On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote:
> joe@cuddy[503]: export TERM=xterm-color
> joe@cuddy[504]: vi
> xterm-color: Unknown terminal type
> Visual needs addressable cursor or upline capability
> :q
> joe@cuddy[505]: uname -a
> SunOS cuddy 5.6 Generic_105181-16 sun4u sp
On Tue, Jul 18, 2000 at 05:04:20PM -0700, Matthew Hunt wrote:
>
> FWIW, I've just tried "TERM=xterm-color ls -G" inside a
> Solaris xterm, which does not support color. Nothing bad happened.
> The xterm just ignored the color codes instead of producing any
> sort of garbage.
>
> Unless anyone k
On Tue, 18 Jul 2000, Trenton Schulz was heard blurting out:
> On Tue, 18 Jul 2000, Matthew Hunt wrote:
>
> > On Tue, Jul 18, 2000 at 02:16:32PM -0700, Kris Kennaway wrote:
> > > On Tue, 18 Jul 2000, Ron 'The InSaNe One' Rosson wrote:
> > >
> > > > With the change to ls having the 'G' switch add
On Wed, Jul 19, 2000 at 12:55:55AM +0100, Ben Smithurst wrote:
> If that's the case, why don't we change our termcap so that "xterm" and
> "xterm-color" are the same thing, and "xterm-mono" is there for people
> who _reall_ don't want color, or have a monochrome display, or whatever.
> It seems r
Matthew Hunt wrote:
> Does anyone know why XFree86's xterm, as shipped, doesn't set
> TERM to xterm-color? Is it for fear of an xterm-color entry
> not existing (either on the local machine, or machines you
> telnet/ssh to from the xterm)?
ok, next question.
If that's the case, why don't we ch
13 matches
Mail list logo
