-
-
Notifications
You must be signed in to change notification settings - Fork 548
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
fix: Replace mapfile
to support Bash 3.2.57 pre-installed in macOS
#627
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
5deea8c
[`hooks/_common.sh`] Replace `mapfile` to support older Bash
yermulnik bf354a2
Declare `dir_paths_unique` as local and as array
yermulnik a272c33
Address PR discussion by creating array in a one-liner
yermulnik 310cf28
Apply suggestions from code review
MaxymVlasov 2f9dfe9
Apply suggestions from code review
MaxymVlasov ebd7079
pre-commit fixes
24ac3cf
Address remark about array elements splitting
yermulnik 2e14c16
Resolve merge conflict
yermulnik File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well it was replaced to
mapfile
from https://www.shellcheck.net/wiki/SC2207Maybe we'd prefer a more readable variant than all this
read IFS ololo done <<< | )
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link that you refer to has this at the very top =)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, and I don't think that it is problematic, as paths must be split by spaces, just by
tr ' ' '\n'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have no spaces in paths which can be split accidentally
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while read
approach. Else we need to replace otherwhile read
bits with the "other" solution.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good shout out. But... but if between three of us one says "canonical" is less readable, while
var=($(command))
is, then I reckon we have to provide readability and clarity for that one of us who prefers specific solution over other solution unless that preferred solution breaks for someone else (when we stumble upon someone with newlines in dir/file names 🤪).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And even then we will just need to use a proper separator of
\0
, though this may require us to deal with diffs between BSD and GNUsort
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And now code from #629
I don't get it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I got it. This is about
IFS
and*
.Ok, #629 works.
Apologies for the confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect you're seeing differences because you're passing the params to a function, which means they're passing through an extra layer of quoting.
This code works for me on MacOS, with both v3 and v5: