-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manpage #565
base: main
Are you sure you want to change the base?
Manpage #565
Conversation
While Markdown isn't the best fit for writing manpages, it's the easiest for future contributions/maintenance. However, pandoc is a heavy dependency for producing a single manpage. Other tools [1] could be evaluated. The only pandoc-isms are the title block [2] (first 3 lines) which will rarely change, and the definition lists ':' for options which is self-explanatory. The Markdown source is intentionally not hard wrapped. pandoc automatically hard wraps the roff man output (which may be further re-wrapped by manpage viewers). To produce the manpage (outputs a file Cemu.1): pandoc -s -f markdown-smart -t man Cemu.1.md -o Cemu.1 Preview from Markdown without writing to file: pandoc -s -f markdown-smart -t man Cemu.1.md | man -l - markdown-smart *disables* the smart typography extension to avoid mangling '--'. [3] [1]: https://drewdevault.com/2018/05/13/scdoc.html [2]: https://pandoc.org/MANUAL.html#extension-pandoc_title_block [3]: https://pandoc.org/MANUAL.html#extensions
The roff manpage produced by pandoc is included in this commit, as well as a plaintext preview of what it would look like when viewed with 'man' in a terminal of 80 width.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of shipping a pre-generated artefact, could you please add a man
target to the CMake build system instead?
First of all thank you for bringing this up!
I personally don't fully agree with the opinion expressed in the
Cemu is licensed under the MPL-2.0
I'd only describe the files used in "non portable" mode, and then mention that in portable mode everything is more or less dumped in the binary directory. |
I'm not including the actual manpage. The 2nd commit is just for preview here. But I can't do the CMake thing, because
I know, I was asking for an existing statement (if any) like |
Il giorno ven 9 dic 2022 alle 08:57:06 -08:00:00, jn64
***@***.***> ha scritto:
I'm not including the actual manpage. The 2nd commit is just for
preview here.
Oh ok, I wasn't sure about that, thanks for the clarification :)
But I can't do the CMake thing, because
I don't know how, and don't intend to learn, and As mentioned in the
first commit, this would add a build dependency on pandoc (or
whatever intermediate format chosen), which should be decided on
first.
No worries, I can do it instead (either in a follow-up patch or by
posting a diff here). Also, the intermediate format processor chosen
doesn't have to be a hard build dependency; I'd first check if pandoc
(or whatever) is available, and add the man target only if it is.
…--
OpenPGP key: 66DE F152 8299 0C21 99EF A801 A8A1 28A8 AB1C EE49
|
It's supposed to be a fully formed URL pointing to the NNID API server, such as
Cemu/src/config/LaunchSettings.cpp Lines 179 to 187 in cd3fe06
Though last time I checked these arguments haven't been working for a long time (since before Cemu 2.0 even came out), and seem to have been replaced with other config options? Cemu/src/config/LaunchSettings.cpp Lines 279 to 282 in cd3fe06
|
See commit messages for details
Todo:
AUTHORS — I took it from the About dialog of Cemu. Some manpages include "and contributors" or similar wording, or simply omit AUTHORS.--act-url
argument "URL prefix for account server" is (protocol? hostname or part of hostname? fully formed URL?)