| 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.
|
|
😵💫
Trying to get back the sense of sharp contrast I had before.
Snippets from *scratch* in case I need to recompute some of these:
(defun my/color-hsl-to-rgbhex (h s l)
(apply
'color-rgb-to-hex
`(,@(color-hsl-to-rgb h s l) 2)))
(defun my/color-hs1-l2 (c1 c2)
(pcase-let ((`(,h1 ,s1 _) (apply 'color-rgb-to-hsl
(color-name-to-rgb c1)))
(`(_ _ ,l2) (apply 'color-rgb-to-hsl
(color-name-to-rgb c2))))
(message "hue %.3f with s %.3f l %.3f" h1 s1 l2)
(apply 'color-rgb-to-hex
`(,@(color-hsl-to-rgb h1 s1 l2) 2))))
(defun my/modus-rgb (key palette)
(let ((value (car (alist-get key palette))))
(if (stringp value)
value
(car (alist-get value palette)))))
(list-colors-display
(list (my/modus-rgb 'bg-completion modus-vivendi-palette)
(my/color-hs1-l2 (my/modus-rgb 'bg-completion modus-vivendi-palette)
"#303030")
(my/color-hs1-l2 (my/modus-rgb 'bg-completion modus-vivendi-palette)
"#202020")))
(pcase-dolist (`(,sym ,val)
modus-vivendi-palette)
(when-let ((color (and (string-match "bg-\\(.*\\)-subtle" (symbol-name sym))
(match-string 1 (symbol-name sym))))
(darker (color-darken-name val 40.0)))
(message "%s (%s): %.2f"
color
val
(modus-themes-contrast val (car (alist-get (intern color) modus-vivendi-palette))))
(message "%s (%s): %.2f"
color
darker
(modus-themes-contrast darker
(car (alist-get (intern color) modus-vivendi-palette))))))
(dolist (diffkind '(removed changed))
(dolist (suffix '("" "-faint" "-refine"))
(insert (format "(bg-%s%s \"%s\")\n"
))))
(list-colors-display
(seq-map (pcase-lambda (`(,h ,l))
(apply 'color-rgb-to-hex `(,@(color-hsl-to-rgb h 1.0 l) 2)))
'((0.00 0.04)
(0.00 0.08)
(0.00 0.16)
(0.59 0.04)
(0.59 0.08)
(0.59 0.16)
(0.12 0.04)
(0.12 0.08)
(0.12 0.16))))
|
|
FTR, things that I expect to need further tweaks and/or discussions
with Prot:
(a) no "version" command, so it's kind of hard to guess what we are
working with programmatically,
(b) preset palettes overrides are unavailable before loading the
themes, and we can't require 'modus-themes either; maybe the
manual should point out that users who want to use those presets
should (1) do that in :config (2) load the theme twice?
(c) lots of backgrounds look very light/saturated to me even in the
"faint preset": e.g. diff backgrounds, selected completion,
region, eldoc current argument.
|
|
|
|
Try as I might, I can't get my fingers to reach for underscores when
my brain is thinking of *equality signs.
|
|
I don't use any of the auto-deferring keywords; setting this shaves a
bit off my startup time (5s ↘ 3.2s).
|
|
This reverts commit d3e251ac8ac4ee953fe24234b4ff4755a185b494.
Will customize use-package-always-defer instead.
|
|
Since I'm not using it anymore.
|
|
|
|
|
|
|
|
Also move it up, closer to Custom-related stuff.
|
|
Also update package list:
- account eglot and use-package being built-in
- add a couple of packages for Emacs development (elisp-benchmarks,
gnus-mock)
- remove paradox (most features now built into vanilla package.el)
|
|
Following the advice from (modus-themes) Sample configuration with and
without use-package.
|
|
That one was a doozy.
|
|
Undecided about C-c bindings. I like having them in "one neat pile",
rather than scattered across several use-package forms.
|
|
|
|
|
|
|
|
|
|
In order to copy/paste between word processors and Emacs markup modes.
This needs a bit more work (e.g. when copying Org snippets, we need to
siphon some #+ macros and copy any #+SETUPFILEs) but it's a start.
|
|
|
|
|
|
|
|
(window-buffer window-to-split) returns nil in that case, because
window-to-split is the root of the "window tree" rather than a "leaf"
or "live" window with an actual buffer attached to it.
|
|
|
|
Emacs seems to take margins into account when deciding whether a
window can be split horizontally. So with my current personal config,
a full-width Gnus article window would have huge margins, and could
not be split horizontally because a half-width window would not have
enough room for these margins.
|
|
Move other MLs further down to keep things alphabetized 🤓
|
|
So as not to catch e.g. <https://static.lwn.net/kerneldoc/>.
|
|
Lots of commands in Gnus buffers try to reinstate the setup defined in
gnus-buffer-configuration, so when eg drafting a message with the
original article displayed on the side, and using P or N to move
around the thread, there ends up being some friction in window
management.
So stop using the Group buffer as a way to left-pad articles; it
doesn't even look good on half-width frames anyway.
|
|
Make it more outline-friendly.
|
|
Couple of mistakes there:
* buffer-local-value was called too late,
* the symbol wasn't quoted, so buffer-local-value ended up taking a
peek at fill-column directly, because that's what my/centered-width
defaults to.
Just wrap the whole thing in with-current-buffer. That'll make it
easier to introduce new buffer-local variables set via mode hooks.
|
|
|
|
|
|
See <https://lwn.net/Articles/902796/bigpage#Briefs>.
|
|
|
|
|
|
Moving around in Rust code is a pretty nerve-racking experience
otherwise.
|
|
|
