| Age | Commit message (Collapse) | Author |
|---|
|
No idea how I managed to commit it in such a non-working state.
|
|
|
|
|
|
Would have added some backgrounds, but the faces (vc-dir-header &
vc-dir-status-edited in particular) are applied on too much
surrounding whitespace, so empty space becomes "lit up" and
distracting.
|
|
I update somewhat infrequently, and more often than not some packages
will fail to compile for obscure reasons.
At this stage, I've done the "generate minimal .emacs with selected
packages, install from scratch" dance that I figure I might as well
automate it.
|
|
The stuff about package-initialize is flat out wrong:
(a) package-initialize is _not_ called automatically at startup;
(b) for all that, customizations seem none the worse for wear.
'(elisp) Packaging Basics' suggests that Emacs does automatically call
'package-activate-all' (unless asked otherwise in the early init file)
so it's really not clear what that business with package-initialize
was about 🤷
Add some more up-to-date commentary regarding other topics.
|
|
Not sure why I thought this cross-reference "format" was a good idea.
Perhaps because it works even if 'calendar' is not loaded? OTOH C-x
C-e vomits the docstring to the echo area, so meh.
|
|
* .emacs (my/run-strip-newline): New escape hatch, to let my/run DTRT
most of the time and spare most callers the cognitive load.
(my/run): Heed it. Document.
(my/kill-command): New helper; meant for programmatic use where
arglists are manipulated as lists, and and no shell escaping is
required.
(my/kill-date, my/describe-revision): Use it.
(my/kill-shell): Document, to disambiguate with my/kill-command.
|
|
Comes up often enough, e.g. to add a stamp to a filename; probably was
the original motivation for my/kill-shell.
Gave a honest attempt at using a transient for this, but got bogged
down second-guessing whether I should define my arguments as
shorthands inside my transient-define-prefix form, or as dedicated
transient-define-argument forms; gave up while trying to figure out
whether the shorthand form could use transient-read-date.
|
|
|
|
IIUC the previous version ran customizations immediately during
expansion (ultimately expanding to the last customize-set-variable
value), instead of generating forms that would run those
customizations at appropriate times.
Guess I never run Emacs <29 😐
|
|
Also move more customizations to use-package forms.
|
|
Been using that for literal years at $DAYJOB; no idea why it's taken
me this long to port to my personal config.
|
|
The previous code failed to detect some HTML emails, perhaps because
the text/html part was nested inside a multipart/alternative?
Lucked onto debbugs-gnu.el by asking xref for occurrences of
gnus-article-mime-handles in the Emacs tree; not sure if M-? showing
results from ~/.emacs.d/elpa was intended, but it sure helped here.
|
|
It's probably more idiomatic to run a testcase you are developing in
your own session, using 'M-x ert' commands? I figure starting a fresh
Emacs cannot hurt.
|
|
gnus-article-prepare-hook is _not_ run in the article buffer. No idea
why things fall into place on my desktop; probably some ill-defined
buffer-switching plumbing.
Also clarify nearby comment.
|
|
Unhappy with those timestamps, but somewhat less unhappy than when I
started.
Also
* remove erc-fill-wrap: as mentioned in the comments, it causes
intempestive recentering;
* remove erc-notifications-mode; redundant with 'notifications' in
erc-modules.
|
|
Letting visual-line-mode take care of wrapping.
|
|
By tricking shr into treating tables like regular blocks.
|
|
Matches my usage pattern better.
|
|
Since the article buffer is re-used, visual-line-mode will keep its
previous state if not explicitly set. So before the patch
1. I display article 1, which should be wrapped: the hook sets
visual-line-mode to t,
2. I display article 2, which should not be wrapped: truncate-lines is
set to t, but visual-line-mode remains t (not a biggie, truncate-lines
"wins"),
3. I decide I want to wrap article 2, so I call the visual-line-mode
toggling command: visual-line-mode is set to nil; seemingly nothing
happens.
This patch dispels the confusion.
|
|
Set shr-fill-text to nil; this automatically causes eww to enable
visual-line-mode.
For Gnus, the dance is a bit more involved. Not 100% happy with where
I landed, but at least I gave myself an escape hatch by rebinding C-c
d v in summary buffers.
Also,
* lift size restriction when fontifying citations: it mostly only ever
causes fontification failures when people review big patches,
* tweak header order slightly,
* align shr heading faces with eighters-title-* faces.
|
|
|
|
|
|
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.
|
