latexmlc does not open the documentation #792
Closed
Comments
I think latexmlc never printed the full help on screen. It's a bit of a tricky thing there, since I've been meaning to reuse the POD in Common::Config, but I never found out how without copying it verbatim. So this is not a regression, latexmlc has always been a little different is all. It's a good request to make this better. |
In the end you were right - I actually had some smart code in place that was displaying the synopsis from Common::Config on Thanks for the report, very helpful! |
Glad it's been helpful! |
physikerwelt
added a commit
to physikerwelt/LaTeXML
that referenced
this issue
Aug 24, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Up to a few weeks ago, the commands
latexml* --help
used to print the help directly in the terminal.Then, the behavior changed into printing just the version information and opening the man page (which is fine for me). On the latest git version & Ubuntu 14.04, the commands
latexml --help
andlatexmlpost --help
are equivalent toman latexml
andman latexmlpost
(at least, on my system).However,
latexmlc
does not follow this behavior. The commandlatexmlc --help
just prints the version number on the terminal and nothing else. If I try to access the man page viaman latexmlc
, I get a quite scant manpage with the following synopsis:To get a clue of what the options for
latexmlc
are, I have to typeman LaTeXML::Common::Config
and go through a couple of screens before getting into the section "OPTION SYNOPSIS" that indeed describes the options forlatexmls/latexmlc
.I think this is not really "user friendly", since it makes quite hard for a user to find the information he is looking for. It would be nice, imho, to
latexmlc --help
toman latexmlc
, as it already happens withlatexml
andlatexmlpost
;latexmlc
, as it used to be a few weeks ago (afair).I hope this is not just a problem with my configuration, so let me kindly know if you can reproduce the bug.
The text was updated successfully, but these errors were encountered: