On Sep 21, 2005, at 14:19, Florian Ernst wrote:
Uh, what type of configuration is this? BTW, you cannot disable the
fruit salad via an option, but you could always set the terminal type,
i.e. "TERM=vt100 hexedit $file" should give you plain black and white.
Or is it just that the colours should be chosen differently?
I mean, I wouldn't upload a package that is generally unusable...
I set the back/foreground colors depending on the host, so the text
gets difficult to read in several cases. Yes, I could just set
another color, or downgrade the terminal definition, _but_ I was just
happy before this change, and for binary files I just don't consider
color so important (in fact, it really looks like a fruit salad in
most cases).
The problem here is that this new feature provides additional
functionality und thus might enhance the usability, but at the same
time
seems to cause some trouble for some users. The feature cannot be
enabled or disabled during runtime, but it can be overridden to not
come into effect as mentioned above, so it seems natural to enable it
when compiling the package.
Yes, I saw the patch, I know it's not your fault, but enabling
features conditionally is really poor programming. What if I provide
a patch that adds a "--color" switch instead, like most other utilities?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
