Re: tail

2001-05-01 Thread Matthew Hunt
ORK, ">tmp/" or die "$!"' Is a directory at -e line 1. wopr:~$ perl -e 'open SPORK, "tmp/" or die "$!"' wopr:~$ (See also "man 2 open".) -- Matthew Hunt <[EMAIL PROTECTED]> * Clearly there are more things in the http://ww

Re: installworld : problem 2 (parallelism: -j 2/3/4)

1999-08-20 Thread Matthew Hunt
both -- build and > install. To do just about anything in our source tree or ports collection, make(1) has to parse a lot of Makefile lines. On my slow CPU with decent I/O, "make installworld" and "make clean" are quite CPU-bound. -- Matthew Hunt <[EMAIL PROTECTED]> * Sta

Re: Color ls

2000-07-18 Thread Matthew Hunt
ignored the color codes instead of producing any sort of garbage. Unless anyone knows of an xterm that barfs on color codes, I would support this change. -- Matthew Hunt <[EMAIL PROTECTED]> * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: Color ls

2000-07-18 Thread Matthew Hunt
neric_105181-16 sun4u sparc SUNW,Ultra-1 That's not the issue. What we want to do is have TERM=xterm be the same as xterm-color is now. If you log in to a FreeBSD box from your Sun, and *then* set TERM=xterm-color and run things on the FreeBSD box, do the color escape sequences screw anyt

Re: Color ls

2000-07-18 Thread Matthew Hunt
f you log in to a machine which is like FreeBSD is now; you won't get color unless you switch back to "xterm-color". The goal is to have TERM=xterm do the color thing when possible and not give the problem you describe by setting TERM=xterm-color and logging in t

Re: Color ls

2000-07-18 Thread Matthew Hunt
are about. Tell me what my proposed solution breaks, for real. -- Matthew Hunt <[EMAIL PROTECTED]> * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message