| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
Also make code comments outline-compliant.
|
|
Mainly for heading-like elements; keeping more colorful variants for
syntax constructs in programming languages.
|
|
|
|
Write down the method to the madness.
|
|
The rules I'm trying to adhere to:
1. theme faces, then standard faces, then third-parties;
2. if keeping a group of faces together makes maintenance easier,
define a "subgroup" and sort it at the end;
3. keep things sorted lexicographically, unless another order makes
sense (e.g. section hierarchy) and it's too much of a hassle to add
groups of comments.
|
|
By dimming hiding the common parts more.
|
|
Pops more; also somewhat consistent with the idea that it's a key
binding.
|
|
|
|
- bg #0 0 0
- bg-dim #1 1 1 → bg-hl-dimmer #0f0f0f
- bg-hl-dim #1a1a1a → bg-hl-dim #181818
- bg-hl #2 2 2
Dimmer:
- buttons
- fringe
- key bindings
- inactive mode line
- tab bar
- diff header 1 (command)
- diff header 2 (file)
- ediff unfocused hunks
- magit focused section
- magit focused hunk content
Dim:
- Custom editable fields (comment, field widget)
- highlight
- diff header 3 (hunk & function)
- magit unfocused hunk heading
Least dim:
- button box
- magit focused hunk heading
|
|
Nonplussed with Modus v4.
|
|
Also move them to .emacs.d. If some other program needs them, I guess
I'll make an ~/.icons folder or something.
Also break the 80-column rule 😨
|
