Tweak IMPLICIT_COMMAND_DEPENDENCIES man entry#4856
Merged
Conversation
Tighten up wording, remove example that adds no value. Clarifies one ambiguity: the oringal text could be read as implying if IMPLICIT_COMMAND_DEPENDENCIES is set to one, the first word of each command in a segmented line is scanned, but the implementation in this case applies the "lightweight" CommandAction scanner, which is documented as: "Lightweight dependency scanning involves only scanning the first entry in an action string, even if it contains &&.". The new wording matches this behavior. Along the way, updated the rest of the the non-code references to Python to use the entity &Python;. Signed-off-by: Mats Wichmann <mats@linux.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Tighten up wording, remove example that adds no value.
Clarifies one ambiguity: the oringal text could be read as implying if
IMPLICIT_COMMAND_DEPENDENCIESis set to one, the first word of each command in a segmented line is scanned, but the implementation in this case applies the "lightweight"CommandActionscanner, which is documented as: "Lightweight dependency scanning involves only scanning the first entry in an action string, even if it contains &&.". The new wording matches this behavior.Along the way, updated the rest of the the non-code references to Python to use the entity
&Python;.This is a doc-only change.
As implied earlier, I have consolidated my manpage changes from this release cycle into a single entry in CHANGES; nothing was adjusted in RELEASE since the structure of that document already has a separate documentation section, and so was already clear enough. This change implies there will be minor merge work if this PR is merged before the other pending ones that have CHANGES.txt diffs. It should be minor fiddling only.
Contributor Checklist:
CHANGES.txtandRELEASE.txt(and read theREADME.rst).