lucaspiller wrote:

Probably is a good idea, but it might be nicer just to say "Version: blah blah blah", i.e.:

Version: 0.4.0.1
Version: r3308

It may be a bit confusion if people see "Revision: r3308".

As for the patch, seems ok, but might be nicer with the spaces between blocks back in (see attached version).

Attachments

• append_version_to_help-2.patch (0.76 KiB)

This comment was imported from FlySpray: https://bugs.openttd.org/task/15#comment39

Qball wrote:

yes I did think about that... But shouldn't it be Version: bla bla when it's a stable release. and only telling revision when it's a svn build? is this possible?

Problem is, in my eye's, that calling it "Version: 0.4.0.1, Revision: r3308" isn't correct. It aint version 0.4.0.1, its a pre 5.0 or 4.5 or whatever the new version is going to be. But this aint a big problem. maybe call it Version: 0.4.0.1 (Developement) or whatever??

I realy would like a "--version". That is the commen way it's done. But this requires more work.

This comment was imported from FlySpray: https://bugs.openttd.org/task/15#comment40

Qball wrote:

I'll see if I can come up with a patch that also supports long arguments. (like f.e. --video-output).
It doesn't mind if it isnt the most fastest solution, because it's only ran once at startup.

This comment was imported from FlySpray: https://bugs.openttd.org/task/15#comment41

Darkvater wrote:

Aren't there default options for this? Like getopt() but with long arguments :)

Imho it should say: "Version: ". This something is either 0.4.0.1 or r4384 for example, just as what the game and network servers report.

This comment was imported from FlySpray: https://bugs.openttd.org/task/15#comment52

TrueBrain closed the ticket.

Reason for closing: Implemented

Modifieded patch added in r3379

This comment was imported from FlySpray: https://bugs.openttd.org/task/15