Date:	Fri, 28 Apr 2000 18:13:07 -0400 (EDT)
Message-Id:	<200004282213.SAA26938@indy.delorie.com>
From:	Eli Zaretskii <eliz AT delorie DOT com>
To:	Richard Dawe <richdawe AT bigfoot DOT com>
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<39089981.16E7FAF7@bigfoot.com> (message from Richard Dawe on
	Thu, 27 Apr 2000 20:48:17 +0100)
Subject:	Re: Some questions about porting fileutils 4.0
References:	<39081435 DOT E2EDBC04 AT bigfoot DOT com> <39089981 DOT 16E7FAF7 AT bigfoot DOT com>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Thu, 27 Apr 2000 20:48:17 +0100
> From: Richard Dawe <richdawe AT bigfoot DOT com>
> 
> The port seems to be going OK so far - I've got all the programs to build.
> I've only applied a few of the diffs from fileutils 3.16 port - you seem
> to have done much of the work for me already Eli. ;)

I'd suggest to scrutinize each change I did, and also look for things
I didn't do, but which should be done now.  It's been a long time
since Fileutils 3.16 were ported (and most of the ground-breaking work
was actually done on Fileutils 3.12 and 3.13 before that), so it's
quite possible that the new features in DJGPP need different
decisions.

For example, the code in dircolors.c which looks at the shell name
should probably be made workable with DOS-style sh.exe and such, what
with so many people who use Bash for interactive sessions.

> I have one question: in the patch from fileutils 3.16 port for dircolors.c
> there is a line #ifdef'd on __DJGPP__ that _always_ sets the 'term'
> variable to "console". In non-DJGPP cases the terminal is obtained from
> the TERM environment variable. Is there any reason why we shouldn't allow
> the TERM env var to override "console", e.g. for output redirection?

Probably not.  But could you please explain more about what do you
want to do here?  I'm not sure I understand the details of your plan.

- Raw text -