Am Sun, 30 Apr 2017 00:56:40 -0500 schrieb R0b0t1 <r03...@gmail.com>:
> On Sun, Apr 30, 2017 at 12:14 AM, Kai Krakow <hurikha...@gmail.com> > wrote: > > Am Sat, 29 Apr 2017 14:39:13 +0000 > > schrieb Alan Mackenzie <a...@muc.de>: > > > >> For a start, I could barely read parts of it, which were displayed > >> in dark blue text on a black background. Setting > >> up /etc/portage/color.map is not the first thing a new user should > >> have to do to be able to read messages from emerge. This is, > >> however, something I knew had to be done, and I did it. > > > > This is a problem with most terminal emulators having a much too > > dark "dark blue". On an old DOS CRT, this dark blue was still > > bright enough to be read easily on black background. Especially, I > > found PuTTY in Windows having a dark blue barely readable. > > > > E.g., in KDE Konsole I usually switch to a different terminal color > > scheme which usually gets around this. But then, contrast on bright > > colors is usually very bad, as can be seen in MC at some points. But > > the new "breeze" color scheme from current Plasma versions is quite > > nice and an overall good fit. > > > > I have occasionally had this problem (and the reverse - green and > yellow are unreadable on light backgrounds), but the default colors in > URxvt are fairly reasonable. Much depends on a reasonable color palette in the terminal emulator. There are only few that get it right. > Not to derail this thread but what is the process for getting changes > into the handbook? I have some suggestions as well, but still only > have a vague idea of how it is maintained. There's a lot that could be > added in relation to maintaining modern systems, and many of the > changes to portage could be added. (E.g. there's people who will come > into the IRC and have a conglomeration of settings that, based on the > quirks and naming conventions, you can tell were taken from 3-4 places > each being published years apart. There probably needs to be some > basic information all in one place.) There's the Gentoo wiki. I don't know if you need special privileges or if it's open to everyone to put in improvements. And then, there's always the BGO (bugs.gentoo.org) where you can suggest even handbook improvements by selecting the proper bug component. > And in reply to the Perl problem, though my response probably isn't > needed: I can verify that using a high backtrack number solved this, > and that the dependency chain was the longest I have seen save one > other time. Usually, using "reinstall-atoms" works much better for me (and it's faster in most cases because when emerge dumps all those stuff and I see it's easily resolvable by reinstall-atoms, I do that, instead of using a high backtrack value, waiting for ages again, only to see that it may not solve my problem). -- Regards, Kai Replies to list-only preferred.
