Fix #83 and #30.

[ciechowoj]

Fix #83: New multiline translation.
Fix #30: Single space inserted after function names.

I know that there was a discussion (#30) about adding formatting features to dstep with some negative arguments, but it doesn't cost much to add them, they can save some time for some people and apparently there is a need for them from some users (at least two at the moment).

[jacob-carlborg]

Would it be possible to have both a positive and negative argument, like --space-after-function-name and --no-space-after-function-name. This is quite common for Posix commands, see git add --help where there is a --[no-]ignore-removal command, for an example.

[ciechowoj]

It cannot be done automatically with getopt. The only way I see is to add a negation of given option to Configuration and check the constraints in code. Something like:

 "no-space-after-function-name", "Do not put a space after a function name.", &config.noSpaceAfterFunctionName,
 "space-after-function-name", "Put a space after a function name.", &config.spaceAfterFunctionName);

/+ ... +/

if (config.noSpaceAfterFunctionName && config.spaceAfterFunctionName) {
    // very bad
}

[jacob-carlborg]

Then we'll leave it as is.

[ciechowoj]

I rethought the matter and getopt seems to support assigning of a true and false to the CLI switch. Maybe it would be better to resign from no- prefixed switches and require users to specify the desirable value explicitly instead. E.g.

--reduce-aliases=false
--comments=true

I just want to point out that possibility.

[jacob-carlborg]

Yeah, I think that looks better than all the dont... flags.

[jacob-carlborg]

Please add an entry to the changelog as well.

[ciechowoj]

Please add an entry to the changelog as well.

Done.

[jacob-carlborg]

👌

[ciechowoj]

Thanks.