| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is based on the code from notmuch-0.29.3
All values have been defined by:
* for each notmuch-face name
* call describe-face()
* if the face contains any hard-coded colors (such as red, OliveGreen)
then, customize it with zenburn-'color' instead
Signed-off-by: Mattijs Korpershoek <mattijs.korpershoek@gmail.com>
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| | |
More info: https://en.wikipedia.org/wiki/Wikipedia:Zenburn
|
| | |
| |
| | |
When persp-selected-face inherits mode-line like this, the wrong face is used for inactive modelines.
|
| | | |
|
| | |
| |
| | |
This makes it easier for tooling to detect the license.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| | |
Use defcustom instead of defvar.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
the customize interface
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Yes, the variable's symbol prefix really doesn't match the name of the
package.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 8856da44c58193bd6d05b8fd8cfd0c876a12fc87 from
pull-request #300.
Also see #317.
The goal of that commit was to make the diffs prettier by making them
darker, which I agree was a success. Unfortunately the diffs not only
got prettier but also lost information.
The `diff-refine-*' faces quite obviously must be different from the
`magit-diff-*-highlight' faces and the commit being reverted violated
that in the most explicit way possible by making the latter inherit
from the former.
The refinement or "word-level" faces are used to change the parts of
a line that changed. The highlighting faces are used to emphasize
the "selected" part of a diff, e.g. the part of the diff the user is
currently concentrating on by placing the cursor inside that part of
the diff. Obviously if one concentrates on a part of a diff, then
one does not want that part to become *less* informative until one
focuses elsewhere.
I tried fixing this regression without going as far as to completely
reverting the faulty commit, unfortunately I was unable to do so.
|
| | |
| |
| |
| |
| |
| |
| | |
Make the definitions of Magit's Zenburn faces look like those of the
Solarized theme. I now use the latter but used to use the former,
and making this look similar for both themes makes it easier for me
to fix the regressions introduced by others.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Make the definitions of Magit's Zenburn faces look like those of the
Solarized theme. I now use the latter but used to use the former,
and making this look similar for both themes makes it easier for me
to fix the regressions introduced by others.
Do the same for the diff faces.
|
| | |
| |
| |
| | |
Use "C+N" > "C" > "C-N" in all cases.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I originally implemented these advices in #106. They got commented
out in 27cee3d in response to #110 and similar reports in prelude's
issue tracker.
I just implemented the same thing again, only to find the commented
advices once I was done... five years later... it seem I would very
much like this.
So I had a look at the reports and it seems pretty obvious what the
issue was: just because the major-mode is `emacs-lisp-mode', that
does not mean that the buffer is visiting a file. And the fix is
to check whether the buffer is visiting a file before trying to do
something with the `buffer-file-name'.
Besides reverting the commenting and fixing the bug, this commit
also does the following:
- Use `zenburn-default-colors-alist' because that variable has since
been renamed.
- Add out keywords at the end because otherwise the "blue" in
"zenburn-blue" for example would have "blue" as the background color
instead of "zenburn-blue".
- Extend the doc-string of `zenburn-add-font-lock-keywords' to make
users aware of a complication.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
(#324)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I don't think it is customary to add theme groups to any parent group,
but that's probably just because themes are usually not byte-compiled,
so the byte-compiler didn't get a chance to inform the author about
this issue.
The `faces' group seems like an obvious parent. I wouldn't worry
about polluting that group with lots of theme sub-groups if this
catches on because for that to happen all the libraries that define
those themes would have to be loaded and if one did that, then one
would have bigger problems than to many sub-groups.
On the other hand, if one does use the `zenburn' theme (or another
theme), then it is nice to find that in `faces'.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
[dgit --overwrite]
|
| | |\ \
| | | |
| | | |
| | | | |
[dgit --quilt=gbp --overwrite]
|
| | | | |
| | | |
| | | | |
Gbp-Pq: Name patch-README-for-Debian.patch
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Forwarded: not-needed
Gbp-Pq: Name patch-README-for-Debian.patch
|
