aboutsummaryrefslogtreecommitdiff
path: root/TODOs.md
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2021-06-16 12:04:47 -0300
committerEuAndreh <eu@euandre.org>2021-06-16 12:09:56 -0300
commit446c22634db09902dcda6819ddafd3687edddfb1 (patch)
tree28959f78c32e050b839319d673cc6d5760db9291 /TODOs.md
parentaux/: Update (diff)
downloadgit-permalink-446c22634db09902dcda6819ddafd3687edddfb1.tar.gz
git-permalink-446c22634db09902dcda6819ddafd3687edddfb1.tar.xz
TODOs.md: Add #question-e3b7748d-2e67-b60b-e966-ad80c754ea58
Diffstat (limited to 'TODOs.md')
-rw-r--r--TODOs.md31
1 files changed, 31 insertions, 0 deletions
diff --git a/TODOs.md b/TODOs.md
index 33c4e47..9b427ad 100644
--- a/TODOs.md
+++ b/TODOs.md
@@ -113,6 +113,37 @@ part of the first version:
# Questions
+## TODO Is an empty blank line in groff the same as a `.P` request? {#question-e3b7748d-2e67-b60b-e966-ad80c754ea58}
+- TODO in 2021-06-16
+
+---
+
+When reading the manpage with `man` or looking at the final output generated with `pandoc`, it seems to me that an empty line behaves and mean the same thing as a `.P` request.
+If this is true, these two snippets are equivalent:
+
+```troff
+.\" First snippet, using .PP
+
+.PP
+The first paragraph.
+.PP
+The second paragrah.
+.PP
+The third paragraph.
+
+
+.\" Second snippet, using empty lines
+
+The first paragraph.
+
+The second paragrah.
+
+The third paragraph.
+```
+
+I find the second option to be much more readable, and if both are equivalent I prefer writing that.
+In fact, I don't see any reason at all to use `.PP`.
+
# Resources
# Scratch