Paginate the CONFIG command's output

[johnnovak]

Description

As the title says. Displaying our built-in command's help with the /? or -h options does that already, so I've taught CONFIG the same trick.

It really bothered me that I had to make people type in things like CONFIG -h glshader | MORE in the getting started guide. Plus having to pipe things through MORE manually is just an annoyance for everybody.

I've also some made some further enhancements to the output (inserting some new lines here and there).

This fixes the PVS-Studio warnings too that I somehow introduced to main...

Manual testing

Played around with the relevant CONFIG commands, and confirmed the output is now paginated.

Checklist

Please tick the items as you have addressed them. Don't remove items; leave the ones that are not applicable unchecked.

I have:

• followed the project's contributing guidelines and code of conduct.
• performed a self-review of my code.
• commented on the particularly hard-to-understand areas of my code.
• split my work into well-defined, bisectable commits, and I named my commits well.
• applied the appropriate labels (bug, enhancement, refactoring, documentation, etc.)
• checked that all my commits can be built.
• confirmed that my code does not cause performance regressions (e.g., by running the Quake benchmark).
• added unit tests where applicable to prove the correctness of my code and to avoid future regressions.
• made corresponding changes to the documentation or the website according to the documentation guidelines.
• locally verified my website or documentation changes.

[FeralChild64]

Most likely the https://github.com/dosbox-staging/dosbox-staging/blob/jn/paginate-config-output/contrib/resources/translations/README.md file needs a small update. It claims:

Do not exceed 79 characters on a line, or commands such as config -h fullscreen won't be able to display the help properly, and might wrap the text or display blank lines. The limit might be increased to 80 characters in the future, but the implementation is not there yet.

If I understand correctly, the implementation is now done (but I won't have time to test it today).

[FeralChild64]

Another general remark - I fully understand if you consider it out of scope of this PR, but it would be nice to also fix the wrap-around problem I have marked on the screenshot. ideally, the second line with possible values should be indented:

[johnnovak]

Thanks @FeralChild64, I'll take care of these two issues you mentioned in this PR. They seem simple enough.

[johnnovak]

@FeralChild64 80 char long lines are fine now, so I've updated the translation guide.

Only the machine setting has a long list of enum values, nothing else is affected. Frankly, I can't be bothered with that today. I've burned 20 minutes on it, but still not even halfway done, so I'm aborting it...

Raised a ticket for it: #3769

[FeralChild64]

That's perfectly fine - this is a minor issue, and not a regression.

[weirddan455]

This all looks good to me.