Shell Scripting

1367 readers

1 users here now

From Ash, Bash and Csh to Xonsh, Ysh and Zsh; all shell languages are welcome here!

Rules:

Follow Lemmy rules!
Posts must relate to shell scripting. (See bottom of sidebar for more information.)
Only make helpful replies to questions. This is not the place for low effort joke answers.
No discussion about piracy or hacking.
If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!
These rules will change as the community grows.

Keep posts about shell scripting! Here are some guidelines to help:

Allowed: Release Announcement of a command-line program designed for scripted use (e.g. bash, bats, awk, jq, coreutils/moreutils)
Allowed: Tutorials on using shell languages or supplementary tools designed for scripted use
Allowed: Code review/help requests for shell languages or supplementary tools designed for scripted use
NOT Allowed: Announcement of a CLI or TUI program that is not designed for scripted use (Yes, your fancy Zsh plugin which pretty-prints the date and time using only builtins is very cool, but unless you actually want to discuss the code itself, please check out !commandline instead!)
NOT Allowed: Domain-specific tutorials that do not involve shell scripting as a core component (e.g. docker-compose, ansible, nix). If you really love one of these, I'm sure there's a community out there ready to talk about them!
NOT Allowed: Code review requests for non-shell programming languages and configuration languages (e.g. Python, Yaml)

In general, if your submission text is primarily shell code, then it is welcome here!

founded 2 years ago

MODERATORS

snowe

gamma

chaoticAnimals

Pulling variables from functions executed as conditions (self.shell)

submitted 9 months ago by Ballig to c/shell

5 comments fedilink hide all child comments

I've written small bash scripts before, but I bit off a little more this time, and I'm trying to program a little terminal game.

Anyway, I've run into a weird behavior. I have a function that, among other things, writes values to an array and returns either 0 or 1.

If I write echo "${name_of_array[@]}" inside the function, I see the contents of the array printed to standard output.

If I write echo "${name_of_array[@]}" outside the function immediately after executing the function, I see the contents of the array printed to standard output. (So, clearly the array is being treated as a global variable.)

But if I write the following, regardless of which value the function returns, nothing is printed to standard output but an empty line.

if ! name_of_function ; then
 echo "${name_of_array[@]}"
fi

Why is that the case? Doesn't name_of_function get executed when evaluating the if statement? Is this some special case where all variables become local?

I realize I could just assign the function's return value to a separate variable and then use that variable as the condition to the if statement, but it's less elegant, and it doesn't satisfy my curiosity. Is there any way to get the array out of the if statement alone?

It's also possible I'm an idiot and my problem is just some random punctuation somewhere.

you are viewing a single comment's thread
view the rest of the comments

[–] Ballig 1 points 9 months ago

The return value is either 0 or 1.

I don't know enough about coding to know what a variable's scope is. *SearXNG noises* You might be onto something. You think the function is being piped into a subshell?

Brackets didn't seem to help in my script; although maybe I should make a smaller test script just to rule out incompetence. (I'm guessing on the proper syntax for that, something like if ! [[ $(name_of_function "$arguments") ]] ; then, yes?)

I've tried both versions. name_of_array=() in or out of the function, also declare -a -g name_of_array, if I'm remembering those arguments right, at the top of the script.

Thanks for indulging my curiosity; I appreciate it.