Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(api-and-naming): use REPLY for return variable instead of ret #987

Merged
merged 1 commit into from
Dec 24, 2023

Conversation

akinomyoga
Copy link
Collaborator

@akinomyoga akinomyoga force-pushed the REPLY branch 2 times, most recently from e34c89f to 74a7955 Compare November 28, 2023 23:08
@akinomyoga akinomyoga marked this pull request as ready for review November 28, 2023 23:08
@akinomyoga
Copy link
Collaborator Author

The devel version of Bash still has the support for value substitution of the form ${| ... }, which assumes the output variable REPLY.

@@ -7,7 +7,7 @@ inject them to the `COMPREPLY` array variable, as required for completions to
work.

Most other functions make use of "output" variables, i.e. assign values to
them. The most common one of these is named `ret`. Consult the commentary
them. The most common one of these is named `REPLY`. Consult the commentary
Copy link
Owner

@scop scop Dec 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add a few words here why we're using REPLY for this? Uppercase is unconventional, and would be good to note the specific choice of word here as well.

Looks good to me otherwise, pre-approved and good to merge with this addressed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggestion. I separated the sentence of REPLY into a new paragraph and added a description (update: 774454d0..2993392a4).

@akinomyoga akinomyoga force-pushed the REPLY branch 2 times, most recently from 774454d to 7da251f Compare December 24, 2023 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants