memory-leaks

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

commit e21e9dae29ca5d70f5309f793cc70287311282cc
parent c73f455a77669c4e8326d3f3a35139b899b3e0c6
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Tue,  8 Jun 2021 17:15:47 +0200

Do some copyediting

Diffstat:
Mreviews/emacs/hype.org | 22+++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/reviews/emacs/hype.org b/reviews/emacs/hype.org @@ -28,7 +28,7 @@ select a new method. =C-h I <METHOD>= shows what characters input that character with the current input method ("to input: …"). *** What's new The new =C-x \= command enables an input method temporarily, just for -the next character, disables it afterward. +the next character, and disables it afterward. As an occasional user of the =TeX= method, I find this useful because I no longer need to choose between @@ -46,13 +46,13 @@ reckoning. I know [[https://protesilaos.com/codelog/2020-01-07-emacs-display-bu discipline; still, these new commands appeal to my humble caveman brain. -Assuming the command run by key sequence =<KEYSEQ>= will display its -own buffer =<BUF>=, +Assuming the command run by key sequence =KEYSEQ= will display its own +buffer =BUF=, -- =C-x 4 1 <KEYSEQ>= says "please display =<BUF>= right here, in this +- =C-x 4 1 KEYSEQ= says "please display =BUF= right here, in this window"; -- =C-x 4 4 <KEYSEQ>= says "please display =<BUF>= in another window"; -- =C-x 5 5 <KEYSEQ>= says "please display =<BUF>= in another frame". +- =C-x 4 4 KEYSEQ= says "please display =BUF= in another window"; +- =C-x 5 5 KEYSEQ= says "please display =BUF= in another frame". These new ~other-…-prefix~ commands can be seen as generalizations of common shorthands such as =C-x 4 f= or =C-x 5 b=. @@ -73,13 +73,13 @@ I've always been somewhat ambivalent about Emacs's ~kill-ring~: /dammit/ =C-_ C-_= /ah screw it/ =C-h v kill-ring RET C-s= 🤔 And lo! =M-y= now prompts for the ~kill-ring~ item to yank, with -completion. This makes the ~kill-ring~ so much more accessible IMO. +completion. This makes the ~kill-ring~ much more accessible IMO. ** repeat-mode =C-x o o o=! -** ~read-char-by-name-group~, ~read-char-by-name-sort~ +** ~completions-group~, ~read-char-by-name-sort~ Some very welcome quality-of-life tweaks to =C-x 8 RET=. * 27 ** ~what-cursor-show-names~ -Most of my uses of =C-u C-x == are to (re)discover how the Unicode -consortium decided some character should be called; having plain =C-x -== give me that information without popping an extra buffer is neat. +I sometimes use =C-u C-x == to (re)discover how the Unicode consortium +decided some character should be called; having plain =C-x == give me +that information without popping an extra buffer is neat.