Also, if the function does not modify the state of the current shell, and
you want to be able to run it in the background, there is a simple
solution. Simply create a shell script that runs the function.
On Sun, Sep 24, 2017 at 4:44 PM, Mark Volkmann
wrote:
> I see that can enter a command name
On Sun, Sep 24, 2017 at 4:44 PM, Mark Volkmann
wrote:
> I see that can enter a command name (referring to an executable script
> file in PATH) followed by & to run it in the background, but the same
> doesn't seem to work with function names. Is there a reason why those are
> treated differently?
