CLIENT-SPECIFICATION: require support for common as an arg in platform flag #15855
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
github-actions
bot
added
the
documentation
Co-authored-by: Managor <[email protected]>
sebastiaanspeck
approved these changes
Mar 4, 2025
sebastiaanspeck
pushed a commit
to sebastiaanspeck/tldr
that referenced
this pull request
Mar 30, 2025
…m flag (tldr-pages#15855) Co-authored-by: Managor <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
As discussed in #15253 (comment) and in the chatroom this PR updates the client spec to require clients to support passing common as a platform to the platform flag i.e.
tldr -p common some-commandwhen a page exists in the native platform too but is a bit different (i.e. non POSIX, etc).We currently document a lot of POSIX variant pages in common and use the above format to reference pages but it was brought to my notice by a user that some clients (both official and community ones) don't support this behavior yet, this addition ensures that this works the same regardless of the client.