Hi,
Am Sonntag, 10. Jun 2007, 15:06:03 -0500 schrieb Karl Haines:
Color is pretty ;) lol. It makes things interesting! I agree however
that there might need to be some way to turn it off easily.
As far as I see, most e* tools respond on an appended |cat
or have at least a non-color option. Ok,
Am 04.04.2007 um 06:17 schrieb [EMAIL PROTECTED]:
Why do --nocolor and --color=n not work (sys-apps/portage-2.1.2.3)?
Why does the damned thing default to thinking I want blaring bizarre
colors scattered all over my screen?
I fully agree!
But not only for portage (emerge) but for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Color is pretty ;) lol. It makes things interesting! I agree however
that there might need to be some way to turn it off easily.
Robert Welz wrote:
Am 04.04.2007 um 06:17 schrieb [EMAIL PROTECTED]:
Why do --nocolor and --color=n not work
On Sunday 10 June 2007, Karl Haines [EMAIL PROTECTED] wrote about 'Re:
FeatureRequest Was: Re: [gentoo-user] Why are gentoo people so in love
with colorized output?!?':
Color is pretty ;) lol. It makes things interesting! I agree however
that there might need to be some way to turn it off
On 6/10/07, Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
On Sunday 10 June 2007, Karl Haines [EMAIL PROTECTED] wrote about 'Re:
FeatureRequest Was: Re: [gentoo-user] Why are gentoo people so in love
with colorized output?!?':
Color is pretty ;) lol. It makes things interesting! I agree
I also dislike the colorization, but for a more specific reason. Gentoo
seems
to assume one is using white on black rather than the default black on
white
in terminal windows. This makes yellow lettering entirely unreadable to
me.
If I could just change all occurrences of yellow to
Kevin O'Gorman [EMAIL PROTECTED] writes:
I also dislike the colorization, but for a more specific reason. Gentoo seems
to assume one is using white on black rather than the default black on white
in terminal windows. This makes yellow lettering entirely unreadable to me.
If I could just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin O'Gorman wrote:
On 6/10/07, Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
On Sunday 10 June 2007, Karl Haines [EMAIL PROTECTED] wrote about
'Re:
FeatureRequest Was: Re: [gentoo-user] Why are gentoo people so in love
with colorized output
Go back to using Solaris ya old fart!
;)
[EMAIL PROTECTED] wrote:
On Wed, Apr 04, 2007 at 07:36:49AM +0200, Bo ?rsted Andresen wrote:
Weren't you talking about portage? In that case you should obviously file it
against portage.. But yeah, any app that has a --nocolor equivalent that
On Sun, 8 Apr 2007 19:25:03 -0400
David Relson [EMAIL PROTECTED] wrote:
On Sun, 8 Apr 2007 17:56:21 +0100
Neil Bothwick wrote:
Hello Dan Farrell,
Unfortunately, everything above syl.claws 2.4 is masked testing on
x86_64, and I don't want to get my hands dirty on this one.
Hello Dan Farrell,
Hey tony, maybe this is beyond your control, or maybe you don't care,
and if not i respect your autonomy in such matters, but your reply
block punctuation character '|' defeats the very helpful colorization
of my and many other browsers that use the usual '' character to
On Sun, 8 Apr 2007 09:36:20 +0100
Neil Bothwick [EMAIL PROTECTED] wrote:
Hello Dan Farrell,
Hey tony, maybe this is beyond your control, or maybe you don't
care, and if not i respect your autonomy in such matters, but your
reply block punctuation character '|' defeats the very helpful
Hello Dan Farrell,
Unfortunately, everything above syl.claws 2.4 is masked testing on
x86_64, and I don't want to get my hands dirty on this one. Perhaps
one day...
The problem here is that Claws development is proceeding so quickly that
no ebuild gets to spend the normal 30 days in testing
On Sun, 8 Apr 2007 17:56:21 +0100
Neil Bothwick wrote:
Hello Dan Farrell,
Unfortunately, everything above syl.claws 2.4 is masked testing on
x86_64, and I don't want to get my hands dirty on this one. Perhaps
one day...
The problem here is that Claws development is proceeding so
On Thu, 05 Apr 2007 21:07:02 +0200
Tony Stohne [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mick said the following on 2007-04-05 19:07:
| ...
| Hmm, neither less not cat give me color output. Passing --color=y
to either
| tells me things like:
|
Dan Farrell said the following on 2007-04-07 19:26:
Hey tony, maybe this is beyond your control, or maybe you don't care,
and if not i respect your autonomy in such matters, but your reply
block punctuation character '|' defeats the very helpful colorization
of my and many other browsers that
W.Kenworthy [EMAIL PROTECTED] writes:
What I would like to know is why less in a console does give colour
syntax highlighting, but does NOT do so in any of the X terminals Ive
tried ...
Or why when run in a console the output stays on the screen when you
exit less, thus allowing you to refer
Hello Graham Murray,
Or why when run in a console the output stays on the screen when you
exit less, thus allowing you to refer to it when typing the next
command, but in an X terminal it 'collapses' to just the command
prompt on exit.
That one was enough to get me to switch from less to
Graham Murray wrote:
Or why when run in a console the output stays on the screen when
you exit less, thus allowing you to refer to it when typing the
next command, but in an X terminal it 'collapses' to just the
command prompt on exit.
If you want the VT behaviour also in X, then alias less
On Fri, 6 Apr 2007, Benno Schulenberg wrote:
Graham Murray wrote:
Or why when run in a console the output stays on the screen when
you exit less, thus allowing you to refer to it when typing the
next command, but in an X terminal it 'collapses' to just the
command prompt on exit.
If
On Thursday 05 April 2007 19:07:33 Mick wrote:
Not really. Just use --color=y if you want colors through a pipe.
Hmm, neither less not cat give me color output. Passing --color=y to
either tells me things like:
--color=y was for emerge to enable colors through a pipe. less needs -R to
show
On Thursday 05 April 2007 20:07, Tony Stohne wrote:
Mick said the following on 2007-04-05 19:07:
| ...
| Hmm, neither less not cat give me color output. Passing --color=y to
either
| tells me things like:
| ==
| There is no color=y option (less --help for
On Friday 06 April 2007 12:06, Bo Ørsted Andresen wrote:
--color=y was for emerge to enable colors through a pipe. less needs -R to
show them.
I'm coming to the conclusion that something must be amiss in my set up because
with or without -R, less shows black white content only.
This is an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mick said the following on 2007-04-06 17:44:
| ...
| That's good. It shows the regexp in colour and makes it easy to find
amidst
| the text. However, what I had in mind was many different colours,
like I can
| see e.g. in vim? Is such a thing
Hi,
Am Dienstag, 03. Apr 2007, 21:17:39 -0700 schrieb [EMAIL PROTECTED]:
Why do --nocolor and --color=n not work (sys-apps/portage-2.1.2.3)?
Why does the damned thing default to thinking I want blaring bizarre
colors scattered all over my screen?
I did not read the whole thread. So this
On Thursday 05 April 2007, [EMAIL PROTECTED] wrote about 'Re: [gentoo-user]
Why are gentoo people so in love with colorized output?!?':
31334
I think you meant 31337.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
[EMAIL PROTECTED] ((_/)o o(\_))
ICQ: 514984 YM
On Wednesday 04 April 2007 07:22, Bo Ørsted Andresen wrote:
On Wednesday 04 April 2007 08:19:47 Graham Murray wrote:
Bo Ørsted Andresen [EMAIL PROTECTED] writes:
First of all I believe most people (including myself) very much prefer
colors over no colors (no I cannot qualify with any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mick said the following on 2007-04-05 19:07:
| ...
| Hmm, neither less not cat give me color output. Passing --color=y to
either
| tells me things like:
| ==
| There is no color=y option (less --help for help)
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony Stohne said the following on 2007-04-05 21:07:
| ...
| To make less interpret color escape sequences, you need the -R option.
| export LESS=-R in your shell startup script and you-ll have it as
| default.
or simply put alias less=less -R,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony Stohne said the following on 2007-04-05 21:14:
| ...
| or simply put alias less=less -R, without the quotes, in your
| ~/.bashrc or in the systemwide bashrc in /etc.
|
Ooops - sorry for the redundant info. I'm a bit tired...
//T
-BEGIN PGP
On Thu, 2007-04-05 at 18:07 +0100, Mick wrote:
On Wednesday 04 April 2007 07:22, Bo Ørsted Andresen wrote:
On Wednesday 04 April 2007 08:19:47 Graham Murray wrote:
Bo Ørsted Andresen [EMAIL PROTECTED] writes:
First of all I believe most people (including myself) very much prefer
...
Bo Ørsted Andresen [EMAIL PROTECTED] writes:
First of all I believe most people (including myself) very much prefer colors
over no colors (no I cannot qualify with any numbers..). That does not,
however, mean that the pipe detection and --color switch etc. shouldn't be
honoured. It should
On Wednesday 04 April 2007 08:19:47 Graham Murray wrote:
Bo Ørsted Andresen [EMAIL PROTECTED] writes:
First of all I believe most people (including myself) very much prefer
colors over no colors (no I cannot qualify with any numbers..). That does
not, however, mean that the pipe detection
Hello Roy Wright,
The beryl negate feature is good for interactive viewing of
these insane color schemes (using both bright yellow and
dark blue in foreground means one or the other will be
impossible to read regardless of background color).
http://gentoo-wiki.com/TIP_Remap_Portage_Colors
On Wed, Apr 04, 2007 at 07:36:49AM +0200, Bo ?rsted Andresen wrote:
Weren't you talking about portage? In that case you should obviously file it
against portage.. But yeah, any app that has a --nocolor equivalent that
doesn't work deserves a bug report.. Even for apps that don't it's
On Tuesday 03 April 2007 23:17:39 [EMAIL PROTECTED] wrote:
[snip: Rant re: portage's stupid color behavior]
Amen. I'm not sure *exactly* what the solution is, but portage needs help
in
the color department.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
[EMAIL PROTECTED]
On Wed, 04 Apr 2007 11:32:45 +0400, [EMAIL PROTECTED] wrote:
On Wed, Apr 04, 2007 at 07:36:49AM +0200, Bo ?rsted Andresen wrote:
Weren't you talking about portage? In that case you should obviously
file it
against portage.. But yeah, any app that has a --nocolor equivalent that
doesn't work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrey Gerasimenko a écrit :
On Wed, 04 Apr 2007 11:32:45 +0400, [EMAIL PROTECTED] wrote:
On Wed, Apr 04, 2007 at 07:36:49AM +0200, Bo ?rsted Andresen wrote:
[snip]
The UNIX standard for ages has been simple text output. Why must
gentoo add
On Wednesday 04 April 2007 09:32:45 [EMAIL PROTECTED] wrote:
Weren't you talking about portage? In that case you should obviously file
it against portage.. But yeah, any app that has a --nocolor equivalent
that doesn't work deserves a bug report.. Even for apps that don't it's
reasonable
On Wednesday 04 April 2007 12:15:40 Andrey Gerasimenko wrote:
Why not create a better color scheme and submit it as a bug report?
Because a 'better' color scheme is a subjective thing. You aren't going to
satisfy everyone and as Neil pointed out you can already define your own
color scheme.
Bo Ørsted Andresen wrote:
On Wednesday 04 April 2007 12:15:40 Andrey Gerasimenko wrote:
Why not create a better color scheme and submit it as a bug report?
Because a 'better' color scheme is a subjective thing. You aren't going to
satisfy everyone and as Neil pointed out you can
On Wed, 04 Apr 2007 16:09:30 +0300, Daniel Iliev wrote:
Exactly. So, MHO is that it would be better if all the output from
console apps was just plain text with the option for people who want
colors to enable and customize colors, wouldn't it?
Why? all you're doing there is changing to a
On Wed, Apr 04, 2007 at 01:37:55PM +0200, Bo ?rsted Andresen wrote:
Both portage (that includes emerge) and revdep-rebuild seems to honour
NOCOLOR=true if put into /etc/make.conf.
No they don't. I have had that line since the day I first noticed it,
and I still get unreadable color output.
[EMAIL PROTECTED] wrote:
On Wed, Apr 04, 2007 at 01:37:55PM +0200, Bo ?rsted Andresen wrote:
Both portage (that includes emerge) and revdep-rebuild seems to honour
NOCOLOR=true if put into /etc/make.conf.
No they don't.
They do here.
Be lucky,
Neil
--
On Wed, Apr 04, 2007 at 03:29:42PM +0100, Neil Bothwick wrote:
On Wed, 04 Apr 2007 16:09:30 +0300, Daniel Iliev wrote:
Exactly. So, MHO is that it would be better if all the output from
console apps was just plain text with the option for people who want
colors to enable and customize
On 4/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
And if ALL THESE CAPS distress you and you think I am shouting, well
goodness gracious, NOW YOU KNOW HOW I FEEL ABOUT COLORIZATION RUN AMUCK.
Caps don't distress me, but they do encourage me to add you to my junk mail
filter.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To add my 2c to this discussion: I am using the latest stable portage
for amd64 (2.1.2.2) and portage respects the --nocolor options. And I am
sure that a non working argument to portage would long ago have been
reported as a bug. So either
On Wednesday 04 April 2007 17:53:21 [EMAIL PROTECTED] wrote:
(b) Switching color off is easier than you might imagine, since all of
the following DO NOT WORK:
TERM=vt100
|less
NOCOLOR=true
--nocolor
--color=n
editing /usr/bin/emerge to always set havecolor = 0
They all work for the
On Wed, 4 Apr 2007 08:53:21 -0700, [EMAIL PROTECTED] wrote:
Why? all you're doing there is changing to a different default colour
scheme (one where all text is the same). I really don't see the point
in changing, when I suspect the majority prefer colours. Switching
colour on and off is
Neil Bothwick ha scritto:
I have felt no need to do the latter, but all the others work for me, as
does editing /etc/portage/color.map.
I was just thinking of suggesting portage to use and honour colour
themes? -this would please both him (using a plain no colour theme) and
us wanting eye
Hello b.n.,
I have felt no need to do the latter, but all the others work for me,
as does editing /etc/portage/color.map.
I was just thinking of suggesting portage to use and honour colour
themes? -this would please both him (using a plain no colour theme) and
us wanting eye candy
b.n. wrote:
However /etc/portage/color.map looks just like what I was
thinking about... except for the fact I can't find it (and
locate tells me nothing too).
I made a man page for it once. Don't know if it's still accurate:
https://bugs.gentoo.org/attachment.cgi?id=89762
Benno
--
On Mittwoch, 4. April 2007, [EMAIL PROTECTED] wrote:
On Wed, Apr 04, 2007 at 03:29:42PM +0100, Neil Bothwick wrote:
On Wed, 04 Apr 2007 16:09:30 +0300, Daniel Iliev wrote:
Exactly. So, MHO is that it would be better if all the output from
console apps was just plain text with the option
Why do --nocolor and --color=n not work (sys-apps/portage-2.1.2.3)?
Why does the damned thing default to thinking I want blaring bizarre
colors scattered all over my screen?
What bozo thought all those colors were legible on every frikking
terminal and checking for --nocolor was unnecesary?
I
On Wednesday 04 April 2007 06:17:39 [EMAIL PROTECTED] wrote:
Why do --nocolor and --color=n not work (sys-apps/portage-2.1.2.3)?
[SNIP]
I am so tired of this crap. Even editing /usr/bin/emerge to always
set output.havecolor to 0 doesn't disable color. I have to copy and
paste into an editor
[EMAIL PROTECTED] wrote:
Why do --nocolor and --color=n not work (sys-apps/portage-2.1.2.3)?
Why does the damned thing default to thinking I want blaring bizarre
colors scattered all over my screen?
What bozo thought all those colors were legible on every frikking
terminal and checking for
On Wed, Apr 04, 2007 at 06:29:45AM +0200, Bo ?rsted Andresen wrote:
On Wednesday 04 April 2007 06:17:39 [EMAIL PROTECTED] wrote:
Why do --nocolor and --color=n not work (sys-apps/portage-2.1.2.3)?
[SNIP]
I am so tired of this crap. Even editing /usr/bin/emerge to always
set
On Wednesday 04 April 2007 07:13:06 [EMAIL PROTECTED] wrote:
I have to copy and paste into an editor just to read the error messages.
Easier to just pipe the output into less.
Doesn't always work. Whatever generates the color ignores TERM and
--nocolor and color=n, and doesn't always
Dale wrote:
I thought I was the only one that had to copy and paste it to Kwrite to
read it. Sorry to say I'm not alone here. :-( He seems, well, . . .
pissed. :/
The beryl negate feature is good for interactive viewing of
these insane color schemes (using both bright yellow and
dark
On Wednesday 04 April 2007 07:48:51 Roy Wright wrote:
echo Syncing overlays...
layman -S
produces email message containing:
Syncing overlays...
svn: Working copy '/usr/portage/local/layman/sunrise' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
details)
60 matches
Mail list logo
