1 files changed, 21 insertions, 4 deletions
diff --git a/itches/emacs/form-feed.md b/itches/emacs/form-feed.md
index 61fd48b..5dd0188 100644
--- a/itches/emacs/form-feed.md
+++ b/itches/emacs/form-feed.md
@@ -19,13 +19,13 @@ You can even see it in source files of other GNU projects, like GCC.
 narrowing commands, yet their default delimiter is displayed as an
 unassuming control character.
 
-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 has actual navigation semantics; 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.
+
 This hypothetical thin-line display could be re-used by e.g.:
 
 - `describe-symbol`, which uses the following method to visually break
@@ -41,7 +41,8 @@ This hypothetical thin-line display could be re-used by e.g.:
 - Custom buffers, where sections are delimited visually with a
   999-character wide underlined space.
 
-(See [emacs-devel][emacs-devel-thin-line] for a use-case recap.)
+(See [emacs-devel][emacs-devel-thin-line] for a list of use-cases for
+thin lines, form-feed-related or not.)
 
 Full disclosure
 :   This reflection started because moving over this underlined space
@@ -54,3 +55,19 @@ Full disclosure
 [`page-break-lines`]: https://github.com/purcell/page-break-lines
 [emacs-devel-thin-line]: https://lists.gnu.org/archive/html/emacs-devel/2019-05/msg00268.html
 [who on Earth]: https://gitlab.com/peniblec/dotfiles/blob/master/.emacs-custom.el
+
+## Scratch pad
+
+In a temporary buffer:
+
+```
+foobar
+^L
+foobaz
+(put-text-property 8 10 'display (propertize "\n" 'face '(:height 0.1 :inverse-video t)))
+```
+
+Possibly needs `:extend t` now?
+
+Grabbing the newline as well as the form-feed could be a way to ensure
+we do not fontify `^L`s embedded in strings?