| 1 |
Here's the kind of output I get from etc-update, for example: |
| 2 |
|
| 3 |
Showing differences between /etc/conf.d/rc and /etc/conf.d/._cfg0000_rc |
| 4 |
ESC[1;31m--- /etc/conf.d/rc 2005-12-22 10:42:50.000000000 +0100ESC[0;0m |
| 5 |
ESC[1;34m+++ /etc/conf.d/._cfg0000_rc 2006-01-07 05:56:06.000000000 |
| 6 |
+0100ESC[0;0m |
| 7 |
ESC[1;35m@@ -35,17 +35,23 @@ESC[0;0m |
| 8 |
ESC[0;0m ESC[0;0m |
| 9 |
ESC[0;0m RC_AUTO_INTERFACE="no"ESC[0;0m |
| 10 |
ESC[0;0m ESC[0;0m |
| 11 |
ESC[1;34m+# RC_DOWN_INTERFACE allows you to specify if RC will bring the |
| 12 |
interfaceESC[0;0m |
| 13 |
ESC[1;34m+# compeletly down when it stops. The default is yes, but there |
| 14 |
are someESC[0;0m |
| 15 |
ESC[1;34m+# instances where you may not want this to happen such as |
| 16 |
using Wake On LAN.ESC[0;0m |
| 17 |
ESC[1;34m+ESC[0;0m |
| 18 |
ESC[1;34m+RC_DOWN_INTERFACE="yes"ESC[0;0m |
| 19 |
ESC[1;34m+ESC[0;0m |
| 20 |
ESC[0;0m # RC_VOLUME_ORDER allows you to specify, or even remove the |
| 21 |
volume setupESC[0;0m |
| 22 |
ESC[0;0m # for various volume managers (MD, EVMS2, LVM, DM, etc). Note |
| 23 |
that they areESC[0;0m |
| 24 |
ESC[0;0m # stopped in reverse order.ESC[0;0m |
| 25 |
ESC[0;0m ESC[0;0m |
| 26 |
ESC[1;31m-RC_VERBOSE="no"ESC[0;0m |
| 27 |
ESC[1;34m+RC_VOLUME_ORDER="raid evms lvm dm"ESC[0;0m |
| 28 |
ESC[0;0m ESC[0;0m |
| 29 |
ESC[0;0m # RC_VERBOSE will make init scripts more verbose. Only |
| 30 |
networking scriptsESC[0;0m |
| 31 |
ESC[0;0m # really use this at this time, and this is useful for trouble |
| 32 |
shootingESC[0;0m |
| 33 |
ESC[0;0m # any issues you may have.ESC[0;0m |
| 34 |
ESC[0;0m ESC[0;0m |
| 35 |
ESC[1;31m-RC_VOLUME_ORDER="raid evms lvm dm"ESC[0;0m |
| 36 |
ESC[1;34m+RC_VERBOSE="no"ESC[0;0m |
| 37 |
ESC[0;0m ESC[0;0m |
| 38 |
ESC[0;0m # RC_BOOTLOG will generate a log of the boot messages shown on |
| 39 |
the console. ESC[0;0m |
| 40 |
ESC[0;0m # Useful for headless machines or debugging. You need to |
| 41 |
emerge the ESC[0;0m |
| 42 |
(END) |
| 43 |
|
| 44 |
Clearly it's working, but.... not. This is in gnome-terminal, but the |
| 45 |
term in use doesn't seem to make any difference, and this is worse than |
| 46 |
nothing at all in terms of readablility (made even worse since using |
| 47 |
colordiff is intended to /enhance/ readability). |
| 48 |
|
| 49 |
Colordiff is set in /etc/etc-update.conf as recommended in the Wiki-- |
| 50 |
diff_command="colordiff -uN %file1 %file2", which seems to be right |
| 51 |
insofar as colordiff is working; it seems to me that the problem is that |
| 52 |
the term is not recognizing/escaping the color codes as color codes, and |
| 53 |
I don't know where to begin to find out why. I'm using the most recent |
| 54 |
colordiff available |
| 55 |
|
| 56 |
eix colordiff |
| 57 |
* app-misc/colordiff |
| 58 |
Available versions: 1.0.3 1.0.4 1.0.5 1.0.5-r2 |
| 59 |
Installed: 1.0.5-r2 |
| 60 |
Homepage: http://colordiff.sourceforge.net/ |
| 61 |
Description: Colorizes output of diff |
| 62 |
|
| 63 |
|
| 64 |
Found 1 matches |
| 65 |
|
| 66 |
and the relevant bug on bgo was fixed ages ago |
| 67 |
|
| 68 |
http://bugs.gentoo.org/show_bug.cgi?id=16924 |
| 69 |
|
| 70 |
So I really have no clue, but I think it must be something I've done wrong. |
| 71 |
|
| 72 |
Does anybody have a clue what that might be? |
| 73 |
|
| 74 |
TIA, |
| 75 |
Holly |
| 76 |
|
| 77 |
|
| 78 |
-- |
| 79 |
gentoo-user@g.o mailing list |
Archives