memory-leaks

Still reachable: lots of words in many pages.
git clone https://git.kevinlegouguec.net/memory-leaks
Log | Files | Refs | README | LICENSE

commit d326965737d2a3c2de1c9239e486a40c6313f8d1
parent dd6c9bafc750ad4cd5fea1c8d2780eb69ef32c6d
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Sat,  7 Jan 2023 18:20:44 +0100

Gush about Emacs tabs

Diffstat:
Mreviews/emacs/hype.org | 10+++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/reviews/emacs/hype.org b/reviews/emacs/hype.org @@ -171,7 +171,7 @@ I've always been somewhat ambivalent about Emacs's ~kill-ring~: And lo! =M-y= now prompts for the ~kill-ring~ item to yank, with completion. This makes the ~kill-ring~ much more accessible IMO. -** repeat-mode +** ~repeat-mode~ =C-x o o o=! ** ~completions-group~, ~read-char-by-name-sort~ Some very welcome quality-of-life tweaks to =C-x 8 RET=. @@ -209,6 +209,14 @@ Previously, =a= (~dired-find-alternate-file~) could be used instead of - =s= :: jump to the *source* definition. *** ~shortdoc-display-group~ Concise reference docs for specific topics. +** Tabs +For a long time I did not bother to check out the new tab bar, since I +did not expect to find a way to make tabs work in my rather byzantine +buffer management. + +Then one day I started playing with the =C-x t= prefix on a whim, and +I was surprised by how much mileage I got out of forking off to a new +tab in order to "tuck away" the current window layout. * 27 ** ~what-cursor-show-names~ I sometimes use =C-u C-x == to (re)discover how the Unicode consortium