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
I tried converting one of my system's manpages with man-to-md and it looked fine in a standalone markdown viewer:
When strip is used with no options on an executable file, it checks that file to see if it uses the dynamic link editor. If it does, the effect of the strip command is the same as using the -u and -r options. If the file does not use the dynamic link editor, the effect of strip without any options is the same as using the -s option of ld(1). The options -S,-x, and -X have the same effect as the ld(1) options. The options to strip(1) can be combined to trim the symbol table to just what is desired.
But when I pasted the generated markdown into a GitHub issue, there were a lot of unnecessary extra linebreaks:
When strip
is used with no options on an executable file, it checks that file to see if it uses the dynamic link editor.
If it does, the effect of the strip
command is the same as using the -u
and -r
options. If the file does not use the dynamic link editor, the effect of strip
without any options is the same as using the -s
option of ld(1).
The options -S, -x,
and -X
have the same effect as the ld(1)
options.
The options to strip(1)
can be combined to trim the symbol table to just what is desired.
Could man-to-md better support GitHub Flavored Markdown?
The text was updated successfully, but these errors were encountered:
I tried converting one of my system's manpages with man-to-md and it looked fine in a standalone markdown viewer:
But when I pasted the generated markdown into a GitHub issue, there were a lot of unnecessary extra linebreaks:
Could man-to-md better support GitHub Flavored Markdown?
The text was updated successfully, but these errors were encountered: