| Age | Commit message (Collapse) | Author |
|
The removed/added backgrounds are too dark for gray10 IMO.
|
|
|
|
|
|
For some reason on openSUSE, I was getting a #232627 cursor whenever I
opened a second frame.
|
|
The keyword face brings too much emphasis to a somewhat
low-information symbol, IMO.
which-key-key-face deserves actual "buttons".
|
|
I'd like to apply serif fonts to Org code blocks as well, but
org-block applies to things other than code…
|
|
|
|
|
|
|
|
|
|
This reverts commit 9bc7b62 (mostly). As of 58fb4c3e68, undefined
:extend attributes in themes now mean "use whatever the original face
definition uses" instead of "nil".
|
|
Never too late.
|
|
|
|
While in there, ask Magit to highlight the current diff context.
|
|
Adjust other backgrounds, especially diff faces.
|
|
Use the button face to hint that tags can be interacted with.
|
|
|
|
|
|
|
|
Hard to read e.g. refined comments.
|
|
Now with an actual formula to compute blends 🙌
Will probably tweak refined faces again to tone the color down.
|
|
|
|
|
|
Also remove TODO for Man-overstrike; I just don't care enough to think
about this.
|
|
- Vanilla tex-mode's faces work fine for me most of the time.
- I don't see the point of adding colors to bold and italic text.
- Shadowed markup is best markup.
- The default color for dark themes is a bit in-your-face.
Also use variable-pitch for outlines (including Org); wooksh pwettyah.
|
|
- diff indicators
- smerge
|
|
|
|
|
|
|
|
Not sure if giving 'shadow the same foreground as comments is a good
idea; the rationale is to limit the number of colors…
|
|
The hunk refinement feature relies on the diff-refine-* faces, which
I customized to use orange and blue. That resulted in red-and-green
sections with orange-and-blue words.
I'm not satisfied with the current result though; the blue does not
stand out enough to my taste.
|
|
Someday I'll declare those variables I keep talking about…
|
|
Add this snippet in ~/.Xresouces:
emacs.font: DejaVu Sans Mono-10
Then run xrdb ~/.Xresources.
|
|
I have to think more about the interactions between
- default
- comments
- shadow
- magit-hash
- magit-diff-context-highlight
- magit-diff-hunk-heading
- magit-diff-hunk-heading-highlight
- magit-section-highlight
|
|
Less contrast.
|
|
|
|
|
|
Distinguish active from inactive by making active black-on-white, and
inactive light-grey-on-dark-grey (like comments).
|
|
Not worth this much highlighting.
|
|
|
|
|
|
|
|
|
|
Also:
- emulate the "white on grey" buffer ID from the console
- reduce the contrast on vertical borders
- make header line more prominent
Could be worth defining a single symbol to reuse for vertical-border,
fringe and comments.
|
|
Play with box line width to distinguish between active and inactive
windows.
… I might actually end up taking a liking to putting steel-blue shit
everywhere (eg mode-line box border, vertical-border).)
|
|
Stop :inverting-video by not :inheriting anymore; wrap header-line in
a nice box 🎁.
|
|
I find it's the easiest way to make the following faces work out:
- compilation-mode-line-*
- paradox-mode-line-*
- font-lock-function-name-face, when using eldoc with M-:
Side-effect: now Magit's frame headers are inverted.
|
|
Reduce highlighting; synchronize magit-section-highlight with highlight.
|
|
I could add a comment in there to explain why the fringe's background
needs to be set explicitly, but whatever. My dotfiles are the one
place where I don't have to keep cruft if I don't want to.
|
|
Bold works well enough for emphasis.
|