Jim Meyering wrote: > Bob Proulx wrote: > > I think you identified the problem as being associated with the > > LS_COLORS variable. I am running with 'env -i ...stuff...' and so > > Ah ha! > > With env -i, there would be no TERM setting, so dircolors -b > would output this: > > LS_COLORS=''; > export LS_COLORS
Yes. That looks like it. > So another fix would have been to set e.g., TERM=xterm in the environment. Does the test require a TERM setting to obtain the desired coverage? Automated builds for things like buildbots, and automated distro builds of debs and rpms won't normally have a terminal associated with them. Should I try to test both with and with a terminal? Using something like 'screen' or 'expect' it should be possible to create a terminal environment in the background fairly easily. But I don't think it should be required for the main build and test. Bob _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
