What you may be looking for is the correct "Shebang <https://en.wikipedia.org/wiki/Shebang_(Unix)>" line at the top of the script that determines the interpreter to use (assuming the executable bit has been set.)
Typically I would use something like #!/usr/bin/env bash or, if you want to be specific #!/path/to/your/systems/bash The former will use the bash executable found first in the PATH of the environment of the TiddlyDesktop process; the latter would be preferred unless the script might run on systems where the path to the interpreter my differ, e.g., Macs have an old version of bash by default; while different Linux distributions' bash may be in /bin or /usr/bin. HTH On Friday, January 22, 2021 at 5:14:22 AM UTC-5 TiddlyTweeter wrote: > Ciao Mark S. > > I really looked into it. TBH I can't truthfully reply to your simple > question. > > Background: I using (mainly) Timimi to launch from TW (it is fairly > complex & now retired in the recent version); TiddlyDesktop (fussy, mainly > because it is Chrome inside?); BobEXE (very flexible on scripting; best of > the batch; but overkill for most of my limited needs). > > Outcome: too many variants to address your basic query simply. > > Best wishes > TT > On Monday, 18 January 2021 at 19:30:32 UTC+1 Mark S. wrote: > >> I don't suppose you remember if there was a way to insert spaces? A sh >> script should always know to run itself, but if I could specify >> "/usr/bin/bash ....myshellscript.sh " that should force the system to >> invoke it correctly. >> >> Thanks! >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8fe2412b-48a9-44eb-9931-a946189b7bf8n%40googlegroups.com.
