> The modification to the xterm entry in termcap was made to improve support
> for local xterms, and all other xterms from XFree86.
>
> If we removed this patch, chances are your solaris box could connect
> without problems, but Linux, FreeBSD and other systems using XFree86
> wouldn't be supported as good as possible.
So instead of following a standard, you are choosing to be more compatible
with possibly non-standard clients, and not support standard UNIX systems?
You are adding fancy features to something that should be simple, and by
doing so, breaking compatibility.
That doesn't make sense. I say follow the standards, and let the
non-standard clients be broken. Then it is their problem. I would much
rather have xterms that *work* everywhere, then ones that have fancy
colors and features that only work from other Linux machines.
> The best "fix" I can think of right now is to use some .bashrc script
> that adjusts the TERM setting... Something along the lines of
>
> USERNAME=`id -un`
> REMOTE=`last -ad -n1 $USERNAME |sed -e "s/.* //" |head -n 1`
> if test x$REMOTE = "xsolarixbox.mydomain.com" -o x$REMOTE =
>"xanother.solaris.box.org"; then
> export TERM=xterm-r6
> fi
This isn't a very good fix for the general public. It certainly works
fine for me, and I have no problem with it. The problem still remains
that people are going to be very confused and annoyed if they don't know
what the problem is. You do understand that this problem makes Red Hat
totally unusable in a mixed environment. You should follow standards by
default.
-Randy
> LLaP
> bero
>
> --
> Nobody will ever need more than 640 kB RAM.
> -- Bill Gates, 1983
> Windows 98 requires 16 MB RAM.
> -- Bill Gates, 1999
> Nobody will ever need Windows 98.
> -- logical conclusion
>
>
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
