Re: ansi colors in ports
> Perhaps because it is unneccessary? > IMHO, I prefer the ports infrastructure to be functional, rather than > "nice looking" any day. It could be both ;) Functional is often a result of a nice looking display as well. > -- Eitan Adler "Security is increased by designing for the way humans actually behave." -Jakob Nielsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ansi colors in ports
On Tue, 31 Mar 2009, Sandra Kachelmann wrote: Why does freebsd ports not use ansi colors? This would be so nice :-) Eg. ECHO_MSG would be so much more visible within the compilation soup. Gentoo uses colors too! In fact, some ports do use ansi color for some things. It pretty much depends upon the source. Many applications are written to compile in a variety of environments, including those in which compiling from an ansi-capable terminal is not guaranteed. I think porters should do as little to the source as possible, and that maintaining other applications would be a better use of their time than forcing pretty-pretty on a compile that should run only once. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ansi colors in ports
Hi, On Tue, Mar 31, 2009 at 7:28 PM, Sandra Kachelmann wrote: > Why does freebsd ports not use ansi colors? This would be so nice :-) Perhaps because it is unneccessary? IMHO, I prefer the ports infrastructure to be functional, rather than "nice looking" any day. > Eg. ECHO_MSG would be so much more visible within the compilation > soup. Gentoo uses colors too! Well, if we start using colors as indicators instead of text, how about blind people then? Are we just going to break things for people just because they have bad eyesight? I sure hope not. Those who need to color their output can use tools to do that, like colortail[1]. References: 1) http://www.freshports.org/misc/colortail/ -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Collecting pkg-message files [was: ansi colors in ports]
On Tue, Mar 31, 2009 at 07:28:34PM +0200, Sandra Kachelmann wrote: > Why does freebsd ports not use ansi colors? This would be so nice :-) > Eg. ECHO_MSG would be so much more visible within the compilation > soup. Gentoo uses colors too! I have no comment on using ANSI colors, but I'd like to point something out that I think is more important than coloring build output... During compilation the most important information to users is contained in the pkg-message that is displayed. Traditionally this has shown to be a problem because it often gets pushed into the scrollback buffer. I've got a patch sitting in GNATS about this that I'd like feedback on. It collects all the pkg-message files and displays them in a pager at the end of the build. I'm hoping people will comment on it and it will eventually make it into the tree as I think it will be useful. I know portmaster has a similar behavior which I find quite useful when updating lots of ports. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/122877 -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ansi colors in ports
Why does freebsd ports not use ansi colors? This would be so nice :-) Eg. ECHO_MSG would be so much more visible within the compilation soup. Gentoo uses colors too! Sandra ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
