@prologic (#ipbjj5q) I run my 'local' commands over SSH also? I remember researching this, also did some research now, seems that you can only do this with bash or something like this I guess with temp files? t ``` f() { uname } ``` t2 ``` #!/bin/sh . ./t f ssh -T adi@REMOTE << EOF $(cat t) f EOF ```

@adi (#ipbjj5q) The later is what I'm experimenting with! I'll keep going in this direction. Thank you for the validation! 🙇‍♂️

(#ipbjj5q) @adi Why does this nor work locally? 🤔 foo: ``` $ cat foo foo() { printf "Hello World" } ``` And: ``` $ /bin/sh -c '$(cat foo); foo' /bin/sh: foo(): command not found /bin/sh: foo: command not found ```

(#ipbjj5q) @prologic (#ipbjj5q) Is this a valid function definition? Are we allowed to define the body on the same line? ``` $ cat foo foo() { printf "Hello World" } $ sh foo foo[1]: syntax error: ```{' unmatched ``` ``` $ cat foo foo() { printf "Hello World" } $ /bin/sh -c "$(cat foo); foo" ``` Works well. ``` /bin/sh -c '$(cat foo); foo' ``` Doesn't. I guess is how newlines are processed inside double quotes as opposed to single quotes.```

@adi (#ipbjj5q) Wut?’ 😱

(#ipbjj5q) @adi @prologic No, it's not a newline issue.

@adi (#ipbjj5q) What’s the issue then? I’m out playing table tennis at the moment so I can’t check myself

@adi (#ipbjj5q) if the most compatible way of doing this is with new lines separating the function definition body I’m OK with that