You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's uncomfortable to have the text reach all the way to the edge of the screen. I would suggest allowing the user to use a -m option with an optional value to set the side margins. Could default to 10px if the flag is used but be set to any other quantity of pixels.
The text was updated successfully, but these errors were encountered:
I have the opposite problem. When I use the web server and 'wget' a page, it has no margins, which is what I want. (The README must appear in a tablet.) But when I use --export, the page has margins. So we both need a toggle to explicitly declare when we need margins. (also a table of contents wouldn't suck)
I'm good. --no-inline moves the CSS to files that my browser can't read; then I use string surgery to remove the lines that say <link rel="stylesheet" href="/__/grip/asset/dark_colorblind-3d9d29921e03.css" />. The result is clean HTML with no margins
It's uncomfortable to have the text reach all the way to the edge of the screen. I would suggest allowing the user to use a
-m
option with an optional value to set the side margins. Could default to 10px if the flag is used but be set to any other quantity of pixels.The text was updated successfully, but these errors were encountered: