fix: Extra backslash in config-manpage (Debian Lintian error 734: bad argument name 'P) #1433
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just merging this because the core code base isn't involved and I see risk. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The manpage-generating script no more add an extra backslash to
\\$. The generated manpage now has no syntax errors.Technical details described in the issue #1398.
Looking into the diff it might be radical just to remove the
replace()call. Comparing the manpages generated before and after I couldn't see a negative effect. Also in the future the manpage generation process will get replaced by a new script using pythons code introspection mechanic.Fix #1398