ChatGPT解决这个技术问题 Extra ChatGPT

Loop through an array of strings in Bash?

I want to write a script that loops through 15 strings (array possibly?) Is that possible?

Something like:

for databaseName in listOfNames
then
  # Do something
end

N
Nam G VU

You can use it like this:

## declare an array variable
declare -a arr=("element1" "element2" "element3")

## now loop through the above array
for i in "${arr[@]}"
do
   echo "$i"
   # or do whatever with individual element of the array
done

# You can access them using echo "${arr[0]}", "${arr[1]}" also

Also works for multi-line array declaration

declare -a arr=("element1" 
                "element2" "element3"
                "element4"
                )

Note that the double quotes around "${arr[@]}" are really important. Without them, the for loop will break up the array by substrings separated by any spaces within the strings instead of by whole string elements within the array. ie: if you had declare -a arr=("element 1" "element 2" "element 3"), then for i in ${arr[@]} would mistakenly iterate 6 times since each string becomes 2 substrings separated by the space in the string, whereas for i in "${arr[@]}" would iterate 3 times, correctly, as desired, maintaining each string as a single unit despite having a space in it.
Is array working for old bash versions too ?
I think you don't need to write "declare -a" in front of the name of array variable. It works for me.
thanks for the comment. i spent 2 hours thinking why it worked in command line but not when i ran the script for the same set of commands.
@AndrewKoster here ya go: gnu.org/software/bash/manual/html_node/… Omitting the offset shown in their examples is equivalent to ${array[@]:0} (0 offset AKA start at the beginning). You can easily test this behavior: echo "${array[@]}" and it should be clear why it works this way with for. The double-quotes are good practice any time variables are used, to ensure expected behavior; the fact that they're being used with an array here is coincidental.
O
Ohad Schneider

That is possible, of course.

for databaseName in a b c d e f; do
  # do something like: echo $databaseName
done 

See Bash Loops for, while and until for details.


What is the problem with this approach? In simple cases it seems to work and, then, is more intuitive than @anubhava's answer.
This works particularly well with command substitution, eg for year in $(seq 2000 2013).
The problem is that he asked about iterating through an array.
The 'declare' approach works best if you have to iterate over the same array in more than one place. This approach is cleaner but less flexible.
Why isn't this #1? It's cleaner, and you can easily reuse the array just by setting a string, i.e., DATABASES="a b c d e f".
c
catchdave

None of those answers include a counter...

#!/bin/bash
## declare an array variable
declare -a array=("one" "two" "three")

# get length of an array
arraylength=${#array[@]}

# use for loop to read all values and indexes
for (( i=0; i<${arraylength}; i++ ));
do
  echo "index: $i, value: ${array[$i]}"
done

Output:

index: 0, value: one
index: 1, value: two
index: 2, value: three

That's just for the sake of the example's output with a counter. It's also quite trivial to change that, and works just the same.
The echo at the end is buggy. You don't need to quote constants, you need to quote expansions, or can safely just quote both as follows: echo "$i / ${arraylength} : ${array[$i-1]}" -- otherwise, if your $i contains a glob it'll be expanded, if it contains a tab it'll be changed to a space, etc.
@CharlesDuffy $i won't contain a glob, because it's the loop counter in this example and so you control its value.
@bzeaman, sure -- but if you're sloppy about such things then it requires contextual analysis (as you just did) to prove something correct, and re-analysis if that context changes or the code is reused in a different place or for whatever other reason an unexpected control flow is possible. Write it the robust way and it's correct regardless of context.
This won't work for a sparse array, i.e. if the array is missing elements. For example, if you have array elements A[1]='xx', A[4]='yy' and A[9]='zz', the length will be 3 and the loop won't process all the elements.
C
Community

Yes

for Item in Item1 Item2 Item3 Item4 ;
  do
    echo $Item
  done

Output:

Item1
Item2
Item3
Item4

To preserve spaces; single or double quote list entries and double quote list expansions.

for Item in 'Item 1' 'Item 2' 'Item 3' 'Item 4' ;
  do
    echo "$Item"
  done

Output:

Item 1
Item 2
Item 3
Item 4

To make list over multiple lines

for Item in Item1 \
            Item2 \
            Item3 \
            Item4
  do
    echo $Item
  done

Output:

Item1
Item2
Item3
Item4

Simple list variable

List=( Item1 Item2 Item3 )

or

List=(
      Item1 
      Item2 
      Item3
     )

Display the list variable:

echo ${List[*]}

Output:

Item1 Item2 Item3

Loop through the list:

for Item in ${List[*]} 
  do
    echo $Item 
  done

Output:

Item1
Item2
Item3

Create a function to go through a list:

Loop(){
  for item in ${*} ; 
    do 
      echo ${item} 
    done
}
Loop ${List[*]}

Using the declare keyword (command) to create the list, which is technically called an array:

declare -a List=(
                 "element 1" 
                 "element 2" 
                 "element 3"
                )
for entry in "${List[@]}"
   do
     echo "$entry"
   done

Output:

element 1
element 2
element 3

Creating an associative array. A dictionary:

declare -A continent

continent[Vietnam]=Asia
continent[France]=Europe
continent[Argentina]=America

for item in "${!continent[@]}"; 
  do
    printf "$item is in ${continent[$item]} \n"
  done

Output:

 Argentina is in America
 Vietnam is in Asia
 France is in Europe

CSV variables or files in to a list. Changing the internal field separator from a space, to what ever you want. In the example below it is changed to a comma

List="Item 1,Item 2,Item 3"
Backup_of_internal_field_separator=$IFS
IFS=,
for item in $List; 
  do
    echo $item
  done
IFS=$Backup_of_internal_field_separator

Output:

Item 1
Item 2
Item 3

If need to number them:

` 

this is called a back tick. Put the command inside back ticks.

`command` 

It is next to the number one on your keyboard and or above the tab key, on a standard American English language keyboard.

List=()
Start_count=0
Step_count=0.1
Stop_count=1
for Item in `seq $Start_count $Step_count $Stop_count`
    do 
       List+=(Item_$Item)
    done
for Item in ${List[*]}
    do 
        echo $Item
    done

Output is:

Item_0.0
Item_0.1
Item_0.2
Item_0.3
Item_0.4
Item_0.5
Item_0.6
Item_0.7
Item_0.8
Item_0.9
Item_1.0

Becoming more familiar with bashes behavior:

Create a list in a file

cat <<EOF> List_entries.txt
Item1
Item 2 
'Item 3'
"Item 4"
Item 7 : *
"Item 6 : * "
"Item 6 : *"
Item 8 : $PWD
'Item 8 : $PWD'
"Item 9 : $PWD"
EOF

Read the list file in to a list and display

List=$(cat List_entries.txt)
echo $List
echo '$List'
echo "$List"
echo ${List[*]}
echo '${List[*]}'
echo "${List[*]}"
echo ${List[@]}
echo '${List[@]}'
echo "${List[@]}"

BASH commandline reference manual: Special meaning of certain characters or words to the shell.


THIS IS WRONG. Needs to be "${List[@]}" to be correct, with the quotes. ${List[@]} is wrong. ${List[*]} is wrong. Try List=( "* first item *" "* second item *" ) -- you'll get correct behavior for for item in "${List[@]}"; do echo "$item"; done, but not from any other variant.
Yes special chars do get interpreted , which may or may not be desirable . I updated the answer to include .
I still would strongly suggest showing the more correct/robust approach first. Folks often take the first answer that looks like it'll work; if that answer has hidden caveats, they may only expose themselves later. (It's not just wildcards that are broken by lack of quoting; List=( "first item" "second item" ) will be broken into first, item, second, item as well).
You might also consider avoiding use of an example that might lead people to parse ls output, in contravention of best practices.
You're refuting claims I never made. I'm quite familiar with bash's quoting semantics -- see stackoverflow.com/tags/bash/topusers
C
Community

In the same spirit as 4ndrew's answer:

listOfNames="RA
RB
R C
RD"

# To allow for other whitespace in the string:
# 1. add double quotes around the list variable, or
# 2. see the IFS note (under 'Side Notes')

for databaseName in "$listOfNames"   #  <-- Note: Added "" quotes.
do
  echo "$databaseName"  # (i.e. do action / processing of $databaseName here...)
done

# Outputs
# RA
# RB
# R C
# RD

B. No whitespace in the names:

listOfNames="RA
RB
R C
RD"

for databaseName in $listOfNames  # Note: No quotes
do
  echo "$databaseName"  # (i.e. do action / processing of $databaseName here...)
done

# Outputs
# RA
# RB
# R
# C
# RD

Notes

In the second example, using listOfNames="RA RB R C RD" has the same output.

Other ways to bring in data include:

stdin (listed below),

variables,

an array (the accepted answer),

a file...

Read from stdin

# line delimited (each databaseName is stored on a line)
while read databaseName
do
  echo "$databaseName"  # i.e. do action / processing of $databaseName here...
done # <<< or_another_input_method_here

the bash IFS "field separator to line" [1] delimiter can be specified in the script to allow other whitespace (i.e. IFS='\n', or for MacOS IFS='\r') I like the accepted answer also :) -- I've include these snippets as other helpful ways that also answer the question. Including #!/bin/bash at the top of the script file indicates the execution environment. It took me months to figure out how to code this simply :)

Other Sources (while read loop)


This creates impression that eol is used as string separators and, therefore, whitespaces are allowed within the strings. However, strings with whitespaces are further separated into substrings, which is very very bad. I think that this answer stackoverflow.com/a/23561892/1083704 is better.
@Val, I added code comment with a reference to IFS. (For everyone, IFS lets one specify a specific delimiter, which allows other whitespace to be included in strings without being separated into substrings).
This doesn't work for me. $databaseName just contains the whole list, thus does only a single iteration.
@AlikElzin-kilaka My answer below solves this problem so that the loop is run for every line of the string.
F
Fizer Khan

You can use the syntax of ${arrayName[@]}

#!/bin/bash
# declare an array called files, that contains 3 values
files=( "/etc/passwd" "/etc/group" "/etc/hosts" )
for i in "${files[@]}"
do
    echo "$i"
done

t
tckmn

Surprised that nobody's posted this yet -- if you need the indices of the elements while you're looping through the array, you can do this:

arr=(foo bar baz)

for i in ${!arr[@]}
do
    echo $i "${arr[i]}"
done

Output:

0 foo
1 bar
2 baz

I find this a lot more elegant than the "traditional" for-loop style (for (( i=0; i<${#arr[@]}; i++ ))).

(${!arr[@]} and $i don't need to be quoted because they're just numbers; some would suggest quoting them anyway, but that's just personal preference.)


This really should be the chosen answer. 1: It's simple and easy to read. 2: It handles whitespace correctly, no IFS nonsense is getting in the way. 3: It handles sparse arrays correctly.
T
Treethawat Thanawachiramate

This is also easy to read:

FilePath=(
    "/tmp/path1/"    #FilePath[0]
    "/tmp/path2/"    #FilePath[1]
)

#Loop
for Path in "${FilePath[@]}"
do
    echo "$Path"
done

This one is clear and worked for me (including with spaces and variable substitution in the FilePath array elements) only when I set the IFS variable correctly before the FilePath array definition: IFS=$'\n' This may work for other solutions too in this scenario.
r
rashedcs

Simple way :

arr=("sharlock"  "bomkesh"  "feluda" )  ##declare array

len=${#arr[*]}  # it returns the array length

#iterate with while loop
i=0
while [ $i -lt $len ]
do
    echo ${arr[$i]}
    i=$((i+1))
done


#iterate with for loop
for i in $arr
do
  echo $i
done

#iterate with splice
 echo ${arr[@]:0:3}

K
Kofi

I used this approach for my GitHub updates, and I found it simple.

## declare an array variable
arr_variable=("kofi" "kwame" "Ama")

## now loop through the above array
for i in "${arr_variable[@]}"
do
   echo "$i"


done
   

You can iterate through bash array values using a counter with three-expression (C style) to read all values and indexes for loops syntax:

declare -a kofi=("kofi" "kwame" "Ama")
 
# get the length of the array
length=${#kofi[@]}

for (( j=0; j<${length}; j++ ));
do
  print (f "Current index %d with value %s\n" $j "${kofi[$j]}")
done

a bash array can have holes in it; the correct way to loop through it by index (that also works on associative arrays) is: for i in "${!arr_variable[@]}"; do printf '%d: %s\n' "$i" "${arr_variable[i]}"; done
n
nroose
listOfNames="db_one db_two db_three"
for databaseName in $listOfNames
do
  echo $databaseName
done

or just

for databaseName in db_one db_two db_three
do
  echo $databaseName
done

F
F. Hauri - Give Up GitHub

Implicit array for script or functions:

In addition to anubhava's correct answer: If basic syntax for loop is:

for var in "${arr[@]}" ;do ...$var... ;done

there is a special case in :

When running a script or a function, arguments passed at command lines will be assigned to $@ array variable, you can access by $1, $2, $3, and so on.

This can be populated (for test) by

set -- arg1 arg2 arg3 ...

A loop over this array could be written simply:

for item ;do
    echo "This is item: $item."
  done

Note that the reserved work in is not present and no array name too!

Sample:

set -- arg1 arg2 arg3 ...
for item ;do
    echo "This is item: $item."
  done
This is item: arg1.
This is item: arg2.
This is item: arg3.
This is item: ....

Note that this is same than

for item in "$@";do
    echo "This is item: $item."
  done

Then into a script:

#!/bin/bash

for item ;do
    printf "Doing something with '%s'.\n" "$item"
  done

Save this in a script myscript.sh, chmod +x myscript.sh, then

./myscript.sh arg1 arg2 arg3 ...
Doing something with 'arg1'.
Doing something with 'arg2'.
Doing something with 'arg3'.
Doing something with '...'.

Same in a function:

myfunc() { for item;do cat <<<"Working about '$item'."; done ; }

Then

myfunc item1 tiem2 time3
Working about 'item1'.
Working about 'tiem2'.
Working about 'time3'.

P
Peter Mortensen

The declare array doesn't work for Korn shell. Use the below example for the Korn shell:

promote_sla_chk_lst="cdi xlob"

set -A promote_arry $promote_sla_chk_lst

for i in ${promote_arry[*]};
    do
            echo $i
    done

try the code highlighter in the editor to make your code look good.
Good to know, but this question is about bash.
Lotsa bugs here. Can't have list entries with spaces, can't have list entries with glob characters. for i in ${foo[*]} is basically always the wrong thing -- for i in "${foo[@]}" is the form that preserves the original list's boundaries and prevents glob expansion. And the echo needs to be echo "$i"
P
Peter Mortensen

Try this. It is working and tested.

for k in "${array[@]}"
do
    echo $k
done

# For accessing with the echo command: echo ${array[0]}, ${array[1]}

This does not actually work correctly. Try array=( "hello world" ), or arrray=( "*" ); in the first case it will print hello and world separately, in the second it will print a list of files instead of the *
...before calling something "tested" in shell, be sure to check the corner cases, which whitespace and globs are both among.
J
Jamie

This is similar to user2533809's answer, but each file will be executed as a separate command.

#!/bin/bash
names="RA
RB
R C
RD"

while read -r line; do
    echo line: "$line"
done <<< "$names"

T
The smart Eagle

If you are using Korn shell, there is "set -A databaseName ", else there is "declare -a databaseName"

To write a script working on all shells,

 set -A databaseName=("db1" "db2" ....) ||
        declare -a databaseName=("db1" "db2" ....)
# now loop 
for dbname in "${arr[@]}"
do
   echo "$dbname"  # or whatever

done

It should be work on all shells.


Nope, it doesn't: $ bash --version GNU bash, version 4.3.33(0)-release (amd64-portbld-freebsd10.0) $ set -A databaseName=("db1" "db2" ....) || declare -a databaseName=("db1" "db2" ....) bash: syntax error near unexpected token `('
M
Mahdi-Malv

What I really needed for this was something like this:

for i in $(the_array); do something; done

For instance:

for i in $(ps -aux | grep vlc  | awk '{ print $2 }'); do kill -9 $i; done

(Would kill all processes with vlc in their name)


D
Dan Bray

How you loop through an array, depends on the presence of new line characters. With new line characters separating the array elements, the array can be referred to as "$array", otherwise it should be referred to as "${array[@]}". The following script will make it clear:

#!/bin/bash

mkdir temp
mkdir temp/aaa
mkdir temp/bbb
mkdir temp/ccc
array=$(ls temp)
array1=(aaa bbb ccc)
array2=$(echo -e "aaa\nbbb\nccc")

echo '$array'
echo "$array"
echo
for dirname in "$array"; do
    echo "$dirname"
done
echo
for dirname in "${array[@]}"; do
    echo "$dirname"
done
echo
echo '$array1'
echo "$array1"
echo
for dirname in "$array1"; do
    echo "$dirname"
done
echo
for dirname in "${array1[@]}"; do
    echo "$dirname"
done
echo
echo '$array2'
echo "$array2"
echo
for dirname in "$array2"; do
    echo "$dirname"
done
echo
for dirname in "${array2[@]}"; do
    echo "$dirname"
done
rmdir temp/aaa
rmdir temp/bbb
rmdir temp/ccc
rmdir temp

S
Saurabh Dhage

Declare an array of string with type

declare -a StringArray=("Linux Mint" "Fedora" "Red Hat Linux" "Ubuntu" "Debian" )

Iterate the string array using for loop

for val in ${StringArray[@]}; do
   echo $val
done

Output

https://i.stack.imgur.com/AV59o.png


P
Peter Mortensen

Possible first line of every Bash script/session:

say() { for line in "${@}" ; do printf "%s\n" "${line}" ; done ; }

Use e.g.:

$ aa=( 7 -4 -e ) ; say "${aa[@]}"
7
-4
-e

May consider: echo interprets -e as option here


M
Mohideen bin Mohammed

Single line looping,

 declare -a listOfNames=('db_a' 'db_b' 'db_c')
 for databaseName in ${listOfNames[@]}; do echo $databaseName; done;

you will get an output like this,

db_a
db_b
db_c

P
Peter Mortensen

I loop through an array of my projects for a git pull update:

#!/bin/sh
projects="
web
ios
android
"
for project in $projects do
    cd  $HOME/develop/$project && git pull
end

While this code snippet may solve the question, including an explanation really helps to improve the quality of your post. Remember that you are answering the question for readers in the future, and those people might not know the reasons for your code suggestion. Please also try not to crowd your code with explanatory comments, this reduces the readability of both the code and the explanations!
you should explain IFS variable behavior in your script