Replies: 1 comment
-
This is all done by the jgm/doclayout library. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When editing in terminal Vim under Termux on my phone the width of the screen/virtual line length is limited to 30 columns, and I don't want physical lines to exceed 60 columns because longer physical lines tend to not scroll smoothly. Since I quite often reformat text by running it through pandoc with
-f markdown -t markdown
1 the behavior of Pandoc's--columns
option becomes crucial.Quite understandably with
--columns=60
lines are sometimes shorter than 60 columns due to the presence of long words, which I generally find OK but often they are a bit longer which I find annoying. Generally setting--columns=55
leads to better results but I sometimes get lines longer than 60 columns anyway.So my question is how is line breaking coded to behave? How (much) is it allowed to make lines shorter or longer than the value of
--columns
? Is it by a fixed amount or by a percentage? Are certain character classes ignored? I'm afraid that I don't see the pattern!NB I'm not (yet) calling for a way to prevent overlong lines, just probing for my ideal
--columns
value. So far I have found that results with values between 50 and 55 don't seem to differ substantially from results with 55 while results with 50 results in too many lines which are too short for my liking.Footnotes
Actually using a Vim user command which invokes pandoc using a certain defaults file. ↩
Beta Was this translation helpful? Give feedback.
All reactions