condition to execute

[lisa-asket]

>From: Greg Wooledge <greg@wooledge.org>
>To: help-bash@gnu.org
>Subject: Re: condition to execute
>Date: 07/07/2021 00:54:24 Europe/Paris

>On Tue, Jul 06, 2021 at 11:41:29PM +0200, lisa-asket@perso.be wrote:
>> In elisp, I can return an object from a function using the last command in 
>> the function.
>> 
>> Does this not apply to bash functions as well?

>It does not.

>The quest to make bash (or sh) functions return values to their caller
>is the holy grail of shell scripting. Like the holy grail, it does not
>actually exist, and so the quest can never be fulfilled. But the
>tricks and techniques that people try in pursuit of this goal vary from
>horrific to marginally useful.

>My purpose here is to stop people from using the horrific ones.

>You've already been linked to <https://mywiki.wooledge.org/BashFAQ/084>
>and it's worth repeating. The first page of
><https://mywiki.wooledge.org/BashProgramming> has some more commentary
>about this topic.

>Neither of these web pages is an exhaustive tome of all the possible ways
>to exfiltrate information from inside of a function to the outside world.
>There are certainly other ways, and maybe some day, someone will refine
>some of them to the point where they're worth publishing.

>Until then, recognize bash's limitations, and try to respect the fact
>that those of us who have been working within those limitations for
>decades have acquired some knowledge of what works, and what doesn't.

Am only asking and trying things out.  You should discard the illusion of 
rudeness

and the myth of respect. Where many questions were asked in many parts of the 
world,

usually the questioner dies.  I'm just raising a few questions.  How can a 
question insult

anybody !  A question is just a tool to dig deeper.