Document hashondef and nolog options for POSIX.1-2024 #168
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.
POSIX.1-2024 no longer defines the behavior of the
-h
and-o nolog
options because they are implemented differently in different shells. This commit updates the documentation to reflect this change.Summary by Copilot
This pull request updates the documentation for the
nolog
andhash-on-def
options in both English and Japanese files to clarify their behavior and compatibility with POSIX standards and other shells.Documentation updates:
doc/_set.txt
: Updated the description of thenolog
option to clarify its historical behavior in older Korn shells and its lack of support in modern shells. Added details about thehash-on-def
option, explaining its behavior based on POSIX.1-2001 and noting that POSIX.1-2024 no longer specifies its behavior.doc/ja/_set.txt
: Provided a similar update in Japanese, explaining the historical behavior of thenolog
option and its lack of support in most modern shells. Also added an explanation of thehash-on-def
option's behavior and its evolution in POSIX standards.