Filter a file list against an integer array?How to put the specific files from a directory in an array in bash?How do I aggregate data from many files into one file?How to sum match numbersseparation of files on the basis of their nameFTP script - upload several files with match local folders/ftp foldersUsing awk to process multiple files need to count occurance of variable after pattern. How can I stop array resetting after each file?How to add values to an array which contains a variable in the array name in bash?bash script load an modify array from external filetar “Cannot stat: No such file of directory” when passing array variablesbash command to create array with the 10 most recent images in a dir?
Is there a realtime, uncut video of Saturn V ignition through tower clear?
Good examples of "two is easy, three is hard" in computational sciences
400–430 degrees Celsius heated bath
Does the fact that we can only measure the two-way speed of light undermine the axiom of invariance?
Difference in 1 user doing 1000 iterations and 1000 users doing 1 iteration in Load testing
Why is this python script running in background consuming 100 % CPU?
How could the B-29 bomber back up under its own power?
Is presenting a play showing Military characters in a bad light a crime in the US?
What should I wear to go and sign an employment contract?
Why use nominative in Coniugatio periphrastica passiva?
Does science define life as "beginning at conception"?
Does George B Sperry logo on fold case for photos indicate photographer or case manufacturer?
How should I mix small caps with digits or symbols?
Schwa-less Polysyllabic German Noun Stems of Germanic Origin
Does the Aboleth have expertise in History and Perception?
How to tease a romance without a cat and mouse chase?
How would a physicist explain this starship engine?
How did Arya and the Hound get into King's Landing so easily?
Is my company merging branches wrong?
Why is there no current between two capacitors connected in series?
Story about encounter with hostile aliens
Does a windmilling propeller create more drag than a stopped propeller in an engine out scenario?
Why "strap-on" boosters, and how do other people say it?
Are CTRL+C and <esc> the same?
Filter a file list against an integer array?
How to put the specific files from a directory in an array in bash?How do I aggregate data from many files into one file?How to sum match numbersseparation of files on the basis of their nameFTP script - upload several files with match local folders/ftp foldersUsing awk to process multiple files need to count occurance of variable after pattern. How can I stop array resetting after each file?How to add values to an array which contains a variable in the array name in bash?bash script load an modify array from external filetar “Cannot stat: No such file of directory” when passing array variablesbash command to create array with the 10 most recent images in a dir?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have a folder with lots of images named "clip01234-randomlongstring.png", where 01234 is a random five digit number.
I also have an array "clipnumbers" with a list of integers.
Now I want to create a list "files" containing all file names which match the numbers in the "clipnumbers" array. How would I do that?
The resulting output should be something I can process in the same way as my current list (of all files) I create with: files=($(printf "%sn" *.* | sort -V | tr 'n' ' '))
bash shell-script filenames array
add a comment |
I have a folder with lots of images named "clip01234-randomlongstring.png", where 01234 is a random five digit number.
I also have an array "clipnumbers" with a list of integers.
Now I want to create a list "files" containing all file names which match the numbers in the "clipnumbers" array. How would I do that?
The resulting output should be something I can process in the same way as my current list (of all files) I create with: files=($(printf "%sn" *.* | sort -V | tr 'n' ' '))
bash shell-script filenames array
add a comment |
I have a folder with lots of images named "clip01234-randomlongstring.png", where 01234 is a random five digit number.
I also have an array "clipnumbers" with a list of integers.
Now I want to create a list "files" containing all file names which match the numbers in the "clipnumbers" array. How would I do that?
The resulting output should be something I can process in the same way as my current list (of all files) I create with: files=($(printf "%sn" *.* | sort -V | tr 'n' ' '))
bash shell-script filenames array
I have a folder with lots of images named "clip01234-randomlongstring.png", where 01234 is a random five digit number.
I also have an array "clipnumbers" with a list of integers.
Now I want to create a list "files" containing all file names which match the numbers in the "clipnumbers" array. How would I do that?
The resulting output should be something I can process in the same way as my current list (of all files) I create with: files=($(printf "%sn" *.* | sort -V | tr 'n' ' '))
bash shell-script filenames array
bash shell-script filenames array
edited 59 mins ago
Jeff Schaller♦
45.9k1165150
45.9k1165150
asked 3 hours ago
user3647558user3647558
325
325
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
In a loop:
shopt -s nullglob
files=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
files+=( $pattern )
done
This loops over the numbers and creates a filename globbing pattern for each. The pattern is expanded to add the filenames matching it to the array files
. The nullglob
shell option makes non-matching patterns expand to nothing (as opposed to remain unexpanded).
Using find
(for recursion into all directories beneath the current directory, and for performing some action on each found file):
patterns=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
patterns+=( -o -name "$pattern" )
done
find . -type f ( "$patterns[@]:1" ) -exec action-to-perform-on-files ;
The :1
removes the initial -o
from the list in patterns
in the expansion.
This combines searching for the files with performing some action on them. It would fail if your clipnumbers
array contains many thousands of numbers (the argument list would become too long).
oh wow! i did not see the other posts yet but this here certainly works. it's beautiful! thank you so much, all of you!!!
– user3647558
3 mins ago
add a comment |
Using GNU grep
and printf
:
grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png
Which can be assigned to an array like so:
files=($(grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png))
add a comment |
Option #1
Similar to Kusalananda's answer but with array expansion instead of a loop:
setup
$ touch clip12710-x.png clip30443-x.png clip57592-x.png clip76672-x.png clip93493-x.png
$ declare -a array=([0]="30443" [1]="76672" [2]="42424")
Note that the array contains only two items that are expected to match; there are filenames with clips that are not present and there are clip numbers in array
that do not exist as filenames.
execution
$ shopt -s nullglob
$ pfiles=( "$array[@]/#/clip" )
$ oIFS="$IFS"
$ IFS=
$ pfiles=( $pfiles[@]/%/-*.png )
$ IFS="$oIFS"
$ declare -p pfiles
declare -a pfiles=([0]="clip30443-x.png" [1]="clip76672-x.png")
Note the careful inclusion of double-quotes in the first assignment and the lack of double-quotes in the second assignment. The initial assignment translates the "array" array of numbers into a "pfiles" array of partial filenames by prepending the string clip
to each element. The second assignment appends the -*.png
wildcard to each element of the array; the lack of quoting in this assignment allows the shell to split each element on $IFS
(normally space, tab, and newline), but we've temporarily overridden IFS to be empty. The shell then also "globs" the results, which is what we want here -- for it to expand the "clip...*-png" names into any matching filenames. With the nullglob
shell option set, any non-matching wildcards are dropped. The final result is an array in pfiles of files matching clip numbers from your original array.
Option #2
(ab)use extended globbing:
shopt -s extglob nullglob
declare -a array=([0]="30443" [1]="76672" [2]="42424")
oIFS="$IFS"
IFS='|'
p="$array[*]"
IFS="$oIFS"
pfiles=( clip@($p)-*.png )
This works by setting IFS to the pipe symbol |
so that the subsequent assignment to p
of array[*]
joins the elements of array
by pipes (the first character of $IFS at that point). Pipes are the delimiters that bash's extended globbing syntax requires between options in an extended globbing pattern. The last line expands to an array of files that match the extended glob pattern we've constructed:
- start with
clip
- contain one of the given patterns (clip numbers), now contained in the variable
p
- followed by
-
then anything - and ending in
.png
The nullglob
shell option is required in case your clips array does not overlap with any existing filenames.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f519734%2ffilter-a-file-list-against-an-integer-array%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
In a loop:
shopt -s nullglob
files=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
files+=( $pattern )
done
This loops over the numbers and creates a filename globbing pattern for each. The pattern is expanded to add the filenames matching it to the array files
. The nullglob
shell option makes non-matching patterns expand to nothing (as opposed to remain unexpanded).
Using find
(for recursion into all directories beneath the current directory, and for performing some action on each found file):
patterns=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
patterns+=( -o -name "$pattern" )
done
find . -type f ( "$patterns[@]:1" ) -exec action-to-perform-on-files ;
The :1
removes the initial -o
from the list in patterns
in the expansion.
This combines searching for the files with performing some action on them. It would fail if your clipnumbers
array contains many thousands of numbers (the argument list would become too long).
oh wow! i did not see the other posts yet but this here certainly works. it's beautiful! thank you so much, all of you!!!
– user3647558
3 mins ago
add a comment |
In a loop:
shopt -s nullglob
files=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
files+=( $pattern )
done
This loops over the numbers and creates a filename globbing pattern for each. The pattern is expanded to add the filenames matching it to the array files
. The nullglob
shell option makes non-matching patterns expand to nothing (as opposed to remain unexpanded).
Using find
(for recursion into all directories beneath the current directory, and for performing some action on each found file):
patterns=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
patterns+=( -o -name "$pattern" )
done
find . -type f ( "$patterns[@]:1" ) -exec action-to-perform-on-files ;
The :1
removes the initial -o
from the list in patterns
in the expansion.
This combines searching for the files with performing some action on them. It would fail if your clipnumbers
array contains many thousands of numbers (the argument list would become too long).
oh wow! i did not see the other posts yet but this here certainly works. it's beautiful! thank you so much, all of you!!!
– user3647558
3 mins ago
add a comment |
In a loop:
shopt -s nullglob
files=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
files+=( $pattern )
done
This loops over the numbers and creates a filename globbing pattern for each. The pattern is expanded to add the filenames matching it to the array files
. The nullglob
shell option makes non-matching patterns expand to nothing (as opposed to remain unexpanded).
Using find
(for recursion into all directories beneath the current directory, and for performing some action on each found file):
patterns=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
patterns+=( -o -name "$pattern" )
done
find . -type f ( "$patterns[@]:1" ) -exec action-to-perform-on-files ;
The :1
removes the initial -o
from the list in patterns
in the expansion.
This combines searching for the files with performing some action on them. It would fail if your clipnumbers
array contains many thousands of numbers (the argument list would become too long).
In a loop:
shopt -s nullglob
files=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
files+=( $pattern )
done
This loops over the numbers and creates a filename globbing pattern for each. The pattern is expanded to add the filenames matching it to the array files
. The nullglob
shell option makes non-matching patterns expand to nothing (as opposed to remain unexpanded).
Using find
(for recursion into all directories beneath the current directory, and for performing some action on each found file):
patterns=()
for number in "$clipnumbers[@]"; do
printf -v pattern 'clip%s-*.png' "$number"
patterns+=( -o -name "$pattern" )
done
find . -type f ( "$patterns[@]:1" ) -exec action-to-perform-on-files ;
The :1
removes the initial -o
from the list in patterns
in the expansion.
This combines searching for the files with performing some action on them. It would fail if your clipnumbers
array contains many thousands of numbers (the argument list would become too long).
edited 2 hours ago
answered 3 hours ago
Kusalananda♦Kusalananda
146k18278460
146k18278460
oh wow! i did not see the other posts yet but this here certainly works. it's beautiful! thank you so much, all of you!!!
– user3647558
3 mins ago
add a comment |
oh wow! i did not see the other posts yet but this here certainly works. it's beautiful! thank you so much, all of you!!!
– user3647558
3 mins ago
oh wow! i did not see the other posts yet but this here certainly works. it's beautiful! thank you so much, all of you!!!
– user3647558
3 mins ago
oh wow! i did not see the other posts yet but this here certainly works. it's beautiful! thank you so much, all of you!!!
– user3647558
3 mins ago
add a comment |
Using GNU grep
and printf
:
grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png
Which can be assigned to an array like so:
files=($(grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png))
add a comment |
Using GNU grep
and printf
:
grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png
Which can be assigned to an array like so:
files=($(grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png))
add a comment |
Using GNU grep
and printf
:
grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png
Which can be assigned to an array like so:
files=($(grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png))
Using GNU grep
and printf
:
grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png
Which can be assigned to an array like so:
files=($(grep -F $(printf '%sn' "$clipnumbers[@]") clip?????-randomlongstring.png))
answered 58 mins ago
agcagc
5,01511338
5,01511338
add a comment |
add a comment |
Option #1
Similar to Kusalananda's answer but with array expansion instead of a loop:
setup
$ touch clip12710-x.png clip30443-x.png clip57592-x.png clip76672-x.png clip93493-x.png
$ declare -a array=([0]="30443" [1]="76672" [2]="42424")
Note that the array contains only two items that are expected to match; there are filenames with clips that are not present and there are clip numbers in array
that do not exist as filenames.
execution
$ shopt -s nullglob
$ pfiles=( "$array[@]/#/clip" )
$ oIFS="$IFS"
$ IFS=
$ pfiles=( $pfiles[@]/%/-*.png )
$ IFS="$oIFS"
$ declare -p pfiles
declare -a pfiles=([0]="clip30443-x.png" [1]="clip76672-x.png")
Note the careful inclusion of double-quotes in the first assignment and the lack of double-quotes in the second assignment. The initial assignment translates the "array" array of numbers into a "pfiles" array of partial filenames by prepending the string clip
to each element. The second assignment appends the -*.png
wildcard to each element of the array; the lack of quoting in this assignment allows the shell to split each element on $IFS
(normally space, tab, and newline), but we've temporarily overridden IFS to be empty. The shell then also "globs" the results, which is what we want here -- for it to expand the "clip...*-png" names into any matching filenames. With the nullglob
shell option set, any non-matching wildcards are dropped. The final result is an array in pfiles of files matching clip numbers from your original array.
Option #2
(ab)use extended globbing:
shopt -s extglob nullglob
declare -a array=([0]="30443" [1]="76672" [2]="42424")
oIFS="$IFS"
IFS='|'
p="$array[*]"
IFS="$oIFS"
pfiles=( clip@($p)-*.png )
This works by setting IFS to the pipe symbol |
so that the subsequent assignment to p
of array[*]
joins the elements of array
by pipes (the first character of $IFS at that point). Pipes are the delimiters that bash's extended globbing syntax requires between options in an extended globbing pattern. The last line expands to an array of files that match the extended glob pattern we've constructed:
- start with
clip
- contain one of the given patterns (clip numbers), now contained in the variable
p
- followed by
-
then anything - and ending in
.png
The nullglob
shell option is required in case your clips array does not overlap with any existing filenames.
add a comment |
Option #1
Similar to Kusalananda's answer but with array expansion instead of a loop:
setup
$ touch clip12710-x.png clip30443-x.png clip57592-x.png clip76672-x.png clip93493-x.png
$ declare -a array=([0]="30443" [1]="76672" [2]="42424")
Note that the array contains only two items that are expected to match; there are filenames with clips that are not present and there are clip numbers in array
that do not exist as filenames.
execution
$ shopt -s nullglob
$ pfiles=( "$array[@]/#/clip" )
$ oIFS="$IFS"
$ IFS=
$ pfiles=( $pfiles[@]/%/-*.png )
$ IFS="$oIFS"
$ declare -p pfiles
declare -a pfiles=([0]="clip30443-x.png" [1]="clip76672-x.png")
Note the careful inclusion of double-quotes in the first assignment and the lack of double-quotes in the second assignment. The initial assignment translates the "array" array of numbers into a "pfiles" array of partial filenames by prepending the string clip
to each element. The second assignment appends the -*.png
wildcard to each element of the array; the lack of quoting in this assignment allows the shell to split each element on $IFS
(normally space, tab, and newline), but we've temporarily overridden IFS to be empty. The shell then also "globs" the results, which is what we want here -- for it to expand the "clip...*-png" names into any matching filenames. With the nullglob
shell option set, any non-matching wildcards are dropped. The final result is an array in pfiles of files matching clip numbers from your original array.
Option #2
(ab)use extended globbing:
shopt -s extglob nullglob
declare -a array=([0]="30443" [1]="76672" [2]="42424")
oIFS="$IFS"
IFS='|'
p="$array[*]"
IFS="$oIFS"
pfiles=( clip@($p)-*.png )
This works by setting IFS to the pipe symbol |
so that the subsequent assignment to p
of array[*]
joins the elements of array
by pipes (the first character of $IFS at that point). Pipes are the delimiters that bash's extended globbing syntax requires between options in an extended globbing pattern. The last line expands to an array of files that match the extended glob pattern we've constructed:
- start with
clip
- contain one of the given patterns (clip numbers), now contained in the variable
p
- followed by
-
then anything - and ending in
.png
The nullglob
shell option is required in case your clips array does not overlap with any existing filenames.
add a comment |
Option #1
Similar to Kusalananda's answer but with array expansion instead of a loop:
setup
$ touch clip12710-x.png clip30443-x.png clip57592-x.png clip76672-x.png clip93493-x.png
$ declare -a array=([0]="30443" [1]="76672" [2]="42424")
Note that the array contains only two items that are expected to match; there are filenames with clips that are not present and there are clip numbers in array
that do not exist as filenames.
execution
$ shopt -s nullglob
$ pfiles=( "$array[@]/#/clip" )
$ oIFS="$IFS"
$ IFS=
$ pfiles=( $pfiles[@]/%/-*.png )
$ IFS="$oIFS"
$ declare -p pfiles
declare -a pfiles=([0]="clip30443-x.png" [1]="clip76672-x.png")
Note the careful inclusion of double-quotes in the first assignment and the lack of double-quotes in the second assignment. The initial assignment translates the "array" array of numbers into a "pfiles" array of partial filenames by prepending the string clip
to each element. The second assignment appends the -*.png
wildcard to each element of the array; the lack of quoting in this assignment allows the shell to split each element on $IFS
(normally space, tab, and newline), but we've temporarily overridden IFS to be empty. The shell then also "globs" the results, which is what we want here -- for it to expand the "clip...*-png" names into any matching filenames. With the nullglob
shell option set, any non-matching wildcards are dropped. The final result is an array in pfiles of files matching clip numbers from your original array.
Option #2
(ab)use extended globbing:
shopt -s extglob nullglob
declare -a array=([0]="30443" [1]="76672" [2]="42424")
oIFS="$IFS"
IFS='|'
p="$array[*]"
IFS="$oIFS"
pfiles=( clip@($p)-*.png )
This works by setting IFS to the pipe symbol |
so that the subsequent assignment to p
of array[*]
joins the elements of array
by pipes (the first character of $IFS at that point). Pipes are the delimiters that bash's extended globbing syntax requires between options in an extended globbing pattern. The last line expands to an array of files that match the extended glob pattern we've constructed:
- start with
clip
- contain one of the given patterns (clip numbers), now contained in the variable
p
- followed by
-
then anything - and ending in
.png
The nullglob
shell option is required in case your clips array does not overlap with any existing filenames.
Option #1
Similar to Kusalananda's answer but with array expansion instead of a loop:
setup
$ touch clip12710-x.png clip30443-x.png clip57592-x.png clip76672-x.png clip93493-x.png
$ declare -a array=([0]="30443" [1]="76672" [2]="42424")
Note that the array contains only two items that are expected to match; there are filenames with clips that are not present and there are clip numbers in array
that do not exist as filenames.
execution
$ shopt -s nullglob
$ pfiles=( "$array[@]/#/clip" )
$ oIFS="$IFS"
$ IFS=
$ pfiles=( $pfiles[@]/%/-*.png )
$ IFS="$oIFS"
$ declare -p pfiles
declare -a pfiles=([0]="clip30443-x.png" [1]="clip76672-x.png")
Note the careful inclusion of double-quotes in the first assignment and the lack of double-quotes in the second assignment. The initial assignment translates the "array" array of numbers into a "pfiles" array of partial filenames by prepending the string clip
to each element. The second assignment appends the -*.png
wildcard to each element of the array; the lack of quoting in this assignment allows the shell to split each element on $IFS
(normally space, tab, and newline), but we've temporarily overridden IFS to be empty. The shell then also "globs" the results, which is what we want here -- for it to expand the "clip...*-png" names into any matching filenames. With the nullglob
shell option set, any non-matching wildcards are dropped. The final result is an array in pfiles of files matching clip numbers from your original array.
Option #2
(ab)use extended globbing:
shopt -s extglob nullglob
declare -a array=([0]="30443" [1]="76672" [2]="42424")
oIFS="$IFS"
IFS='|'
p="$array[*]"
IFS="$oIFS"
pfiles=( clip@($p)-*.png )
This works by setting IFS to the pipe symbol |
so that the subsequent assignment to p
of array[*]
joins the elements of array
by pipes (the first character of $IFS at that point). Pipes are the delimiters that bash's extended globbing syntax requires between options in an extended globbing pattern. The last line expands to an array of files that match the extended glob pattern we've constructed:
- start with
clip
- contain one of the given patterns (clip numbers), now contained in the variable
p
- followed by
-
then anything - and ending in
.png
The nullglob
shell option is required in case your clips array does not overlap with any existing filenames.
answered 37 mins ago
Jeff Schaller♦Jeff Schaller
45.9k1165150
45.9k1165150
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f519734%2ffilter-a-file-list-against-an-integer-array%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown