commit c885282b6bd965e6b2a0054b87d8ed4eef997142
parent c0b011dc5755e3cc594d8b80bf7646ac2f979a14
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date: Sat, 9 Feb 2019 12:34:59 +0100
Expand thoughts on form feed display
Diffstat:
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
# Peniblec's Memory Leaks
-## still reachable: 6831 words in 12 pages
+## still reachable: 6844 words in 12 pages
Hi! I am a software engineer interested in [a bunch of things].
diff --git a/personal/itches.md b/personal/itches.md
@@ -296,15 +296,17 @@ source files of other GNU projects, like GCC.
narrowing commands, yet their default delimiter is displayed as an
unassuming control character.
-I like [`page-break-lines`]'s approach; having this kind of display by
-default would make it more obvious that this character serves an
-actual purpose. As it stands, it looks no different from some stray
-CARRIAGE RETURN.
+I like the way form feeds are displayed with [`page-break-lines`];
+magit's `show-lines` blaming style achieves a similar look.
+
+Having this kind of display by default would make it more obvious that
+this character serves an actual purpose; as it stands, it looks no
+different from some stray CARRIAGE RETURN.
This could be re-used by e.g.:
-- `describe-symbol`, which uses the following ~~method~~ hack to
- visually break up multiple symbol definitions:
+- `describe-symbol`, which uses the following method to visually break
+ up multiple symbol definitions:
``` lisp
(insert "\n\n"
