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