memory-leaks

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

commit d4eed1b8f7299caf0db8eae8432febbfb00d6db6
parent 579760792145ce682ad9ea4099e325c38a7cb079
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Sat, 31 Jan 2026 09:45:40 +0100

Spend more words over 'C-x v T'

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

diff --git a/reviews/emacs/hype.org b/reviews/emacs/hype.org @@ -30,19 +30,23 @@ Particularly fond of =C-x v w w= to explore alternate versions of a file; ~magit-find-file~ is still convenient for quickly blaming arbitrary revisions, but visiting an actual checkout allows deploying the full language server & linter gamut. -**** =C-x v [IOT]= prefixes for DWIM diffs with respect to upstreams +**** =C-x v [IOT]= prefixes for DWIM comparisons with upstreams NB: =I= & =O= prefixes are opt-in with =vc-use-incoming-outgoing-prefixes=. -- =I= stands for "incoming" = "what would be pulled", -- =O= stands for "outgoing" = "what would be pushed", -- =T= stands for "topic" and purports to compare the current branch to - its upstream, assuming we are sitting on a transient feature branch - that will eventually be merged back into a longer-lived development - trunk. +- =I= stands for "incoming" = "what we would pull", +- =O= stands for "outgoing" = "what we would push", +- =T= stands for "topic" = "what we would ask /them/ to merge"; + commands in this prefix purport to compare "outstanding" changes + between the current branch and its upstream, assuming we are sitting + on a transient feature branch that will eventually be merged back + into a longer-lived development trunk. Each prefix offers === (fileset diff), =D= (root diff) and =L= (root log). + +For more information about Emacs's understanding of "outstanding +changes", see bug#80006 and [[info:emacs#Outstanding Changes][emacs#Outstanding Changes]]. **** =M-RET=, =M-n= & =M-p= for low-friction Log View movement Partly self-imposed by the decision to split the commit message in the log buffer, and the patch in a separate diff buffer; still, nice to