LC Server: shebang breaks tags?

[matthias_livecode_150811 at m-r-d.de]

i am using 2 scripts for that. Both have the same name but an other extension
One .lc script which contains the complete script and has the <?lc. ?> tags

and one shell script which always looks the same

#! /some/path
put the filename of me into tInclude
replace ".sh" with ".lc" in tInclude
include tInclude

I just have to make sure, that both files have the same name prefix or however this would be called.

This way  i can run my scripts directly on shell and also from the browser if needed.
-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 08.02.2020 um 05:04 schrieb Richard Gaskin via use-livecode <use-livecode at lists.runrev.com>:
> 
> LC Server 6.6 and later allows you to use LC as you would other system utility languages, by including the path to the engine on the first line following a shebang - see discussion here:
> https://livecode.com/livecode-server/
> 
> This lets us use the old MetaCard style with command line scripts, without needing to put "<?lc" and "?>" around the code.
> 
> But oddly, it seems that running a script this way not only doesn't need to comment wrappers, it actually tries to execute them - and of course fails.
> 
> For example, this script:
> 
>    #! ./lcs
> 
>    <?lc
>    put the long date && the long time
>    ?>
> 
> ...throws this error:
> 
>   row 3, col 1: script: not a command (<)
> 
> 
> Weirder, I've found that if I omit the shebang and call the engine directly in the path on the command line it runs well:
> 
>  ./lcs test.lc
> 
> What is it about the shebang that's breaking execution in comment blocks?
> 
> I have a need to embed code within larger blocks of non-code, and had considered using LC Server as a helper app for that.* It doesn't matter much to me if I launch it with the app path or not, but since most of my systems have LC Server installed for general use it would be nice to use the shebang method.  So this seeming anomaly is certainly not critical, just odd.
> 
> 
> 
> * Yes, I know I can use the merge function for this, but LC desktop's merge is far more limited to the implicit merge that happens when using LC Server.
> 
> The merge function doesn't continue code execution across blocks of code separated by non-code, whereas LC Server does this well:
> 
>    <?lc if there is a file "something" then ?>
>    This is some non-code
>    <?lc else ?>
>    Some other non-code
>    <?lc end if ?>
> 
> Maybe we could have the desktop merge function expanded to work like Server's implicit merge?  That would be most awesome.
> 
> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> ____________________________________________________________________
> Ambassador at FourthWorld.com                http://www.FourthWorld.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode