solarized-emacs

commit 320dafa6a79d0c6b286713c49cffad62ea5b657b
parent 30f3995a362baa69678ef486c3674e8f158def29
Author: Thomas Frössman <thomasf@jossystem.se>
Date:   Mon,  6 Apr 2015 07:14:04 +0200

Exemplify base color names usage as used in sol.el

Diffstat:
M
DEV-GUIDE.md
 | 
20
++++++++++----------

1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/DEV-GUIDE.md b/DEV-GUIDE.md
@@ -22,19 +22,19 @@ situations.
 The base Solarized colors have a canonical
 [usage documentation](http://ethanschoonover.com/solarized#usage-development)
 
-Usage table for the dark theme:
-
-* `base 1` - optional emphasized content
-* `base 0` - body text / default code / primary content
-* `base 00` - unspecified (it's a separator)
-* `base 01` - comments / secondary content
-* `base 02` - background highlights
-* `base 03` - background
-
-When defining a child theme, the current convention is to use the dark theme's
+When referring to colors, the convention is to use the dark theme's
 base color names directly, e.g. `(:foreground ,base0)`. They will switch to
 their counterparts automatically in the light theme.
 
+Usage table for the automatic dark/light base colors:
+
+* `,base1` - optional emphasized content
+* `,base0` - body text / default code / primary content
+* `,base00` - unspecified (it's a separator)
+* `,base01` - comments / secondary content
+* `,base02` - background highlights
+* `,base03` - background
+
 ### Basic strategy for selecting colors
 
 The most important general rule is to **avoid color pasta**.