| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
I like that I can get more info about transient commands via faces;
wary of unleashing fruit salads though so keeping it subtle for now.
|
|
And finally get around to setting calendar-intermonth-text.
Re-implement the docstring's example using functions I actually
understand.
|
|
GConf is OBE; GSettings is the replacement, and the configure enables
it by default. What the heck Past Kévin 🤨
|
|
|
|
|
|
|
|
That package is unusual in that it requires… requiring it, in order
to activate its settings. So it's a good candidate for use-package's
:demand t.
It's also a good candidate because something changed in Emacs's Lisp
pretty-printing code, and now customizing anything changes how this
variable is serialized, generating a spurious diff. Can't wait to
have completely moved away from that auto-generated form.
|
|
|
|
* Remove provisions for Emacs<28.
* Move Magit command to my/magit-map.
|
|
This option defaults to 1, which is sub-optimal for groups such as:
nntp+news.gmane.io:gmane.linux.suse.opensuse.devel
nntp+news.gmane.io:gmane.org.misc.sourcehut.general
nntp+news.gmane.io:gmane.comp.gcc.devel
nntp+news.gmane.io:gmane.emacs.help
nntp+news.gmane.io:gmane.emacs.bugs
nntp+news.gmane.io:gmane.emacs.devel
|
|
|
|
Move Python settings to use-package. Tweak a couple of knobs while in
there.
|
|
|
|
|
|
|
|
* "Extra keys" are advertised for non-graphical configurations; as it
happens, they are also useful to provide substitutes for bindings
based on arrow keys.
* Speed commands are nice. Might tweak the predicate some day, but
the default is already useful.
|
|
|
|
Also rename theme commands.
|
|
* "Regular" backgrounds need to pop out more against "dim" ones: this
makes refinements easier to spot within "focused hunks" in Magit.
* Also make dim & subtle foregrounds more saturated. That gives
"poorer" contrast, but it's still legible, and "poorer" contrast is
sort of a design goal for the "dim" variant.
|
|
|
|
… I should go back to Modus.
|
|
* magenta/red is "the current thing"
* cyan is "other things elsewhere that match the thing"
|
|
For stuff that's interesting, but not the main event.
|
|
This came in handy in the revamp soon to be committed.
|
|
This declines a hue for both background and foreground use.
|
|
Mostly to avoid icomplete jank (bug#40152).
Inspired by:
<https://www.scss.tcd.ie/~sulimanm/posts/default-emacs-completion.html>
Rationale for the customizations:
C-M- chord for navigation Because I found myself missing C-n/C-p in
a couple of situations.
auto-help 'visible The feedback is not as immediate as
icomplete, but it's good enough. Tried
'always, but there's a sit-for somewhere
that causes a weird pause if you happen to
RET before bringing up completions.
auto-select 'second-tab M-v? M-g M-c??
show-help nil "Click on a selection to select it" 😏
format 'one-column Where have you been all my life.
max-height 10 More often than not I'm typing something
inspired by the content from another
buffer, so limit how much
context *Completions* can hide.
auto-choose icomplete never clobbered the minibuffer
until I asked it to (with e.g. C-M-i).
Since C-u M-RET is a thing, keep
candidates off the minibuffer unless I
pull them in, in case I change my mind and
start typing something entirely different
from the currently highlighted candidate.
|
|
Puzzled by this problem I have with :hook. "(use-package) Hooks"
suggests that if package X defines function X-foo to be used by
package Y in Y-bar-hook, then the idiomatic thing to do is…
(use-package X
:hook ((Y-bar . X-foo)))
… but empirically, if Y.el contains…
(defcustom Y-bar-hook '(Y-quux Y-corge))
(add-hook 'Y-bar-hook #'Y-grault)
… then Y-bar-hook will be set to '(X-foo Y-grault): it will be missing
the functions added in the defcustom form.
Since add-hook does this:
(or (boundp hook) (set hook nil))
I am assuming that the problem happens when use-package runs X's :hook
additions before Y is loaded. No idea (a) if I can reproduce from -Q
(b) if this is a SNAFU from setting always-defer (c) if this could be
solved by sprinkling :after or :requires.
|
|
|
|
Make region cyan rather than blue, so that the selection remains
visible over added hunks from diff or Magit buffers.
Make Magit selections cyan to follow suit. Make magit-blame headers
blue to fit the "intangible UI" motif.
Look longingly at Modus 4.2 announcement and wonder if this is all
worth it.
|
|
Recent ElDoc & Eglot developments have made the defaults much more
tolerable (the echo area height does not oscillate as much) &
useful (linter warnings are no longer preempted by symbol
documentation).
|
|
|
|
'cause why not.
|
|
|
|
|
|
* ponder magical "kill context so I can paste it into another app"
commands,
* remove obsolete Magit variables,
* make org-goto use the "path completion" UI,
* ponder better buffer names for some buffers.
|
|
|
|
|
|
|
|
|
|
Ideally I'd like Emacs to stop highlighting subcommands altogether,
since it can't properly figure out nested commands, and it does not
append sh-quoted-exec to whatever face is already there, e.g. when
writing a subcommand in a string "$(like this)".
|
|
|
|
|
|
Vector 2022 👏
|
|
* Make header names more "prompt-like" rather than "type-like".
* Tone down header content.
* Remove color for non-MIME attachments.
|
|
|
|
It's going to keep bothering me otherwise.
|
|
OT1H it's likely I'll always keep font-lock's function & built-in
faces somewhat close together (although thinking more about it, the
former is for highlighting declaration, and the latter for
highlighting usage, so… worth challenging that assumption), OTOH I'd
rather not keep the implicit function = directory association.
|
|
Leave font-lock faces alone; just unset shell-font-lock-keywords.
|
