# I am the Watcher. I am your guide through this vast new twtiverse. # # Usage: # https://watcher.sour.is/api/plain/users View list of users and latest twt date. # https://watcher.sour.is/api/plain/twt View all twts. # https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri. # https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject. # # Options: # uri Filter to show a specific users twts. # offset Start index for quey. # limit Count of items to return (going back in time). # # twt range = 1 22 # self = https://watcher.sour.is/conv/ipbjj5q
shops somehow "exports" those functions to where it the check/action items need to be run. There are two runners, local and ssh to consider. Any thoughts on this? Experiences? One thing to keep in mind is I don't particularly want to be locked into a specific shell like Bash for example. I'd rather be as POSIX as we can without too many deps...
shops somehow "exports" those functions to where it the check/action items need to be run. There are two runners, local and ssh to consider. Any thoughts on this? Experiences? One thing to keep in mind is I don't particularly want to be locked into a specific shell like Bash for example. I'd rather be as POSIX as we can without too many deps...
\nf() {\nuname\n}\n\n#!/bin/sh\n\n. ./t\nf\nssh -T adi@REMOTE << EOF\n$(cat t)\nf\nEOF\n
f() {
uname
}
#!/bin/sh
. ./t
f
ssh -T adi@REMOTE << EOF
$(cat t)
f
EOF
\nf() {\nuname\n}\n\n#!/bin/sh\n\n. ./t\nf\nssh -T adi@REMOTE << EOF\n$(cat t)\nf\nEOF\n
$ cat foo
foo() { printf "Hello World" }
$ /bin/sh -c '$(cat foo); foo'
/bin/sh: foo(): command not found
/bin/sh: foo: command not found
$ cat foo
foo() { printf "Hello World" }
$ /bin/sh -c '$(cat foo); foo'
/bin/sh: foo(): command not found
/bin/sh: foo: command not found
\n$ cat foo\nfoo() { printf "Hello World" }\n\n$ /bin/sh -c '$(cat foo); foo'\n/bin/sh: foo(): command not found\n/bin/sh: foo: command not found\n\n$ cat foo\nfoo() { printf "Hello World" }\n$ sh foo\nfoo[1]: syntax error: \n\n\n\nWorks well.\n\n\n\nDoesn't.\n\n I guess is how newlines are processed inside double quotes as opposed to single quotes.
$ cat foo
foo() { printf "Hello World" }
$ sh foo
foo[1]: syntax error:
Works well.
Doesn't.
I guess is how newlines are processed inside double quotes as opposed to single quotes.\n$ cat foo\nfoo() { printf "Hello World" }\n$ sh foo\nfoo[1]: syntax error: \n\n\n\nWorks well.\n\n\n\nDoesn't.\n\n I guess is how newlines are processed inside double quotes as opposed to single quotes.\n$ cat foo\nfoo() { printf "Hello World" }\n$ sh foo\nfoo[1]: syntax error: \n\n\n\nWorks well.\n\n\n\nDoesn't.\n\n I guess is how newlines are processed inside double quotes as opposed to single quotes.