| Age | Commit message (Collapse) | Author |
|
Easier to reach for than \le, especially since I don't enable the TeX
input method as much as I used to.
|
|
See I knew this C-c b keymap would pay for itself.
|
|
bury-buffer is useful as a quick way to dismiss a buffer I've brought
up for a quick glance; rename-buffer helps persist some classes of
buffers (compilation, help, Gnus articles) that get clobbered
otherwise.
|
|
|
|
Commit 2020-09-25 "* CONTRIBUTE: Don't recommend action
stamps" (499848d840) officially disavows action stamps.
|
|
NB: gnus-thread-sort-by-most-recent-{date,number} sometimes fail
because of bug#42334.
|
|
|
|
|
|
I find pcase patterns easier to grok than cons cells, dotted pairs,
cars and cdrs.
|
|
This allows
- which-key to display a helpful symbol instead of "+prefix",
- C-h b to cross-link to the keymap's docstring.
|
|
- Stop requiring quail, since all functions I need are autoloaded.
- Reformat quail-define-package clause ala TeX.
Using the "UTF-8" language environment means the input method now
shows up on C-h L UTF-8.
- Since I might define more input methods, use a more "specific" name.
- Move comment about user bindings where it belongs.
- Make a proper defun, so that which-key can tell me which binding
activates which method.
- Note that docstrings could cross-reference input methods, if not for
help-xref-mule-regexp.
|
|
|
|
C-c map:
- use d for "display" features
- m for "manuals"
- only bind p [cf] when the equivalent C-x binding does not exist.
Org 9.3.7 (future 9.4) now honors electric-indent-mode.
Delight visual-line-mode since I have fringe indicators.
Keep selection highlighted when moving to another window.
|
|
Searching for "KLG" yields fewer false positives than "me".
|
|
I wanted to add 'notifications to the list, started wondering whether
I should change the hook by looping over cons or using append, and got
bored.
For the record, I want to include:
- log
- notifications
and exclude:
- fill
|
|
|
|
- Add ibuffer section for VC buffers.
- Let ERC pick up my full name.
Also, bind switch-to-buffer-obey-display-actions to make C-x 4 4 and
C-x 5 5 more reliable.
|
|
- get rid of diamonds
- don't use sender name if I'm the sender
- fix off-by-one error when humanizing dates
|
|
Take advantage of recent (Emacs 28) additions to project.el to make a
convenient "magit-to-project" command. Some C-c p bindings are now
redundant with the new C-x p keymap; keep them for a bit, as Emacs 28
is not coming out anytime soon.
Add an ibuffer group for "messaging" buffers.
Set lua indentation to 2 spaces; the Lua Style Guide[1] says that this
convention is used in many learning resources; this is also what
pandoc filters use AFAICT.
[1]: http://lua-users.org/wiki/LuaStyleGuide
Org 9.4 introduces a new face for DONE headlines; I think the DONE
keyword face is enough to distinguish these headlines, so I'll turn
off that feature.
|
|
Turns out somebody filed an issue soon after I committed my
workaround:
https://github.com/dajva/rg.el/issues/72
Now fixed 🙌
|
|
|
|
|
|
|
|
|
|
Cf. <https://github.com/dgutov/diff-hl/commit/a625033fb1dde83f6e4c2fc21f632b22ec34b609>.
|
|
|
|
Sometimes, when adding dummy roots, Gnus displays the thread subject
on the first message:
(emacs-devel, fetched from archive.lwn.net)
┌◈
10:31 ├► martin rudalics Re: emacs rendering comparisson between emacs23 and emacs26.3
14:07 │├► Dmitry Gutov
14:35 ││├► Dmitry Gutov
14:45 ││╰► martin rudalics
13:47 │╰► Alan Mackenzie
14:45 ┆ ╰► martin rudalics
And sometimes it doesn't:
(bug-gnu-emacs, fetched from news.gmane.io)
┌◈
02:08 ├► Juri Linkov
05:33 ╰► Stefan Monnier
Adding %S to the dummy line-format will cause the subject to appear
twice in the first situation (on the dummy root, then on the first
message); not great, but better than not knowing what the topic is.
|
|
Frustratingly, sometimes the previous layout gave things like this:
O Yesterday 03:59 ┌◈ Richard Stallman pull requests
O Yesterday 08:54 ├► Eli Zaretskii
03:46 │├► Richard Stallman
O Yesterday 14:00 │╰► Clément Pit-Claudel
O Yesterday 15:05 │ ├► Stefan Monnier
O Yesterday 14:30 │ ╰► Eli Zaretskii
O Yesterday 15:37 │ ╰► Clément Pit-Claudel
Yesterday 16:21 │ ╰► Eli Zaretskii
Yesterday 17:39 │ ├► Clément Pit-Claudel
Yesterday 20:21 │ │╰► Eli Zaretskii
Yesterday 16:41 │ ╰► Dmitry Gutov
Yesterday 20:16 │ ├► Eli Zaretskii
Yesterday 20:24 │ │├► Dmitry Gutov
Yesterday 20:34 │ │╰► 조성빈
Yesterday 20:28 │ ├► Eli Zaretskii
Yesterday 21:39 │ │╰► Dmitry Gutov
03:46 │ ╰► Richard Stallman
O Yesterday 04:49 ╰► Stefan Monnier
03:45 ╰► Richard Stallman
04:03 ╰► Stefan Monnier
O Thu 20:31 ┌◈ Alan Mackenzie Re: emacs rendering comparisson between emacs23 and emacs26.3
O Thu 21:25 ├► Stefan Monnier
O Thu 21:38 ╰► rrandresf@gmail.com
O Yesterday 08:00 ├► Eli Zaretskii
O Yesterday 19:36 │├► andrés ramírez
03:48 │╰► Richard Stallman
08:09 │ ╰► Eli Zaretskii
10:08 │ ╰► Eli Zaretskii
O 03:40 ╰► Richard Stallman
O 10:21 ├► Michael Albinus
10:58 ╰► Eli Zaretskii
11:09 ╰► Eli Zaretskii
12:20 ╰► Ulrich Mueller
I.e. for some reason Alan's response to the "emacs rendering
comparison thread" is not formatted as a false root, and things get
misaligned.
Trying to set gnus-summary-make-false-root to 'empty caused this:
O Thu 20:31 ┌◈ Alan Mackenzie Re: emacs rendering comparisson between emacs23 and emacs26.3
O Thu 21:25 │├► Stefan Monnier
O Thu 21:38 │╰► rrandresf@gmail.com
O 03:40 │ ├► Richard Stallman
O 10:21 │ │├► Michael Albinus
10:58 │ │╰► Eli Zaretskii
11:09 │ │ ╰► Eli Zaretskii
O Yesterday 08:00 │ ╰► Eli Zaretskii
O Yesterday 19:36 │ ├► andrés ramírez
03:48 │ ╰► Richard Stallman
08:09 │ ╰► Eli Zaretskii
10:08 │ ├► Eli Zaretskii
12:43 │ ╰► Alan Mackenzie
12:20 ◈ Ulrich Mueller
Still no false root, and Ulrich's answer is misaligned.
The new settings yield this layout:
┄┐
O Thu 20:31 ├► Alan Mackenzie Re: emacs rendering comparisson between emacs23 and emacs26.3
O Thu 21:25 │├► Stefan Monnier
O Thu 21:38 │╰► rrandresf@gmail.com
O 03:40 │ ├► Richard Stallman
O 10:21 │ │├► Michael Albinus
10:58 │ │╰► Eli Zaretskii
11:09 │ │ ╰► Eli Zaretskii
O Yesterday 08:00 │ ╰► Eli Zaretskii
O Yesterday 19:36 │ ├► andrés ramírez
03:48 │ ╰► Richard Stallman
08:09 │ ╰► Eli Zaretskii
10:08 │ ├► Eli Zaretskii
12:58 │ │╰► Alan Mackenzie
12:43 │ ╰► Alan Mackenzie
13:05 │ ╰► Eli Zaretskii
13:18 │ ├► Alan Mackenzie
13:28 │ │╰► Eli Zaretskii
13:43 │ ╰► Stefan Monnier
12:20 ╰► Ulrich Mueller
It'd be nice if the dummy root held the subject line, but oh well. At
least things are aligned correctly 🙌
|
|
This way subjects are aligned, as well as the names of authors of root
articles.
Use this specific variation of WHITE DIAMOND CONTAINING BLACK …
DIAMOND because it is covered by DejaVu Sans Mono; others require
variable-width fonts.
|
|
Use C-x o with repeatable o instead. This removes a conflict with
Magit and Org bindings.
Inspiration: https://emacs.stackexchange.com/a/52203/10209
|
|
The GUI prompts frequently lack more context, e.g. if I'm using TRAMP
to sudoedit a file, I don't know whether the requested password is for
~/.authinfo.gpg or for superuser authentication.
|
|
This way roots, false roots, first-level line drawings and single
message are aligned.
|
|
Remove nnimap-stream: the default value is good enough, which is a
good thing since I had misspelled it 🤦.
Also tweak Info reference so that I can evaluate it directly.
|
|
Add %* to prevent point from jumping sideways when changing articles.
|
|
Keep false root, otherwise I cannot mark threads with T k.
Apply crude fontification with gnus-face-0.
|
|
Use box drawing characters to show article tree. Don't "adopt"
rootless subthreads as that makes articles look like they answer
unrelated messages.
|
|
AFAICT, by default Gnus threads by *root article* number, oldest
above, newest below.
I'd like to keep the "newest below" logic (messages are sorted within
a thread anyhow), while making sure threads updated recently show
up *below* older threads.
Hence:
- put gnus-thread-sort-by-number first to break ties, following the
recommendation from (gnus) Sorting the Summary Buffer,
- invert gnus-thread-sort-by-most-recent-number, to have
recently-updated threads below older threads.
Not sure this implements exactly what I want (I think I saw some
surprising results here and there), but it seems to come close.
Also note down more useful key bindings.
|
|
|
|
* Use Custom to set whitespace style.
As much as I dislike using Custom for lists where I just want to
add/remove a couple of elements, the previous method introduced a
subtle bug where visiting a diff buffer, *then* activating
whitespace-mode resulted in diff-mode's whitespace style applying
instead of mine. Something to do with diff-setup-whitespace I guess.
* Make Org comply with RET/C-j conventions in the rest of Emacs.
Since Emacs 24.4, by virtue of electric-indent-mode being enabled by
default, RET is the "smart newline" key which handles indentation, and
C-j is the "dumb newline" key which simply inputs character 0x0A.
* Stop popping another frame for Ediff's control buffer.
The popup frame needs its own .Xresources entry. Sometimes it
disappears behind the system tray. Having another window allows
other-windowing.
* Make line-number-mode try harder with long lines.
* Change the scroll logic.
scroll-conservatively > 100 tells Emacs to *never ever* recenter
point, which is annoying when jumping to e.g. a search result or a
tags definition.
scroll-conservatively = n < 100 tells Emacs to recenter when scrolling
needs to move more than n lines, and to scroll only m lines when m≤n.
* And some other stuff.
|
|
So that I can use NNTP to reach bug-gnu-emacs and help-gnu-emacs.
Gmane has moved recently:
https://lars.ingebrigtsen.no/2020/01/15/news-gmane-org-is-now-news-gmane-io/
|
|
|
|
Emacs attempts to expand macros when loading uncompiled files to speed
up their execution. Since rx is not loaded during startup, Emacs is
not aware of the rx pattern for pcase, and takes it for the rx macro.
Since this macro does not understand (let …) forms, it throws an
"unknown rx pattern" error, which interrupts macro-expansion and shows
a noisy warning.
|
|
|
|
|
|
|
|
For reasons not entirely clear, the password prompt would get stuck
when trying to sudoedit a file. minibuffer-depth-indicate-mode told
me that I was 16 prompts deep. I'll chalk if off to my/project-name
calling functions it shouldn't call when TRAMP is busy.
|
|
|
|
|
|
|
|
|