Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

2

Much more robust to use the quoted "@"-form. To see the difference: a=("first element" "2nd elem"); printf "%s\n" ${a[@]}; printf "%s\n" "${a[@]}"

glenn jackman
– glenn jackman

2013-12-11 12:42:48 +00:00
Commented Dec 11, 2013 at 12:42
1

@glennjackman - thanks for the tip, I'll incorporate it. I always forget the @ vs. *. The * makes more sense given it's often assoc. w/ wildcards as "everything". Let me know if I've got it right now.

slm
– slm ♦

2013-12-11 14:44:40 +00:00
Commented Dec 11, 2013 at 14:44
3

Yep that's it: unquoted, both @ and * expand to all the individual words in the array (split on $IFS); quoted, * expands to a single word (joined with $IFS); quoted, @ expands to each array element as a single word.

glenn jackman
– glenn jackman

2013-12-11 15:26:42 +00:00
Commented Dec 11, 2013 at 15:26

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »