Monte Goulding wrote:
>> On 11 Feb 2020, at 6:10 am, Richard Gaskin wrote:
>>
>> Can the merge function be extended to support scripts interleaved
>> between blocks of non-code?
>>
>> e.g. this works in Server, and not in Merge:
>>
>>
>> This is some non-code
>>
>> Some other
> On 11 Feb 2020, at 6:10 am, Richard Gaskin via use-livecode
> wrote:
>
> Can the merge function be extended to support scripts interleaved between
> blocks of non-code?
>
> e.g. this works in Server, and not in Merge:
>
>
> This is some non-code
>
> Some other non-code
Thanks, Monte. With your explanation that does make sense.
I have plenty of options for doing what I need to do, so no worries on
this, but it does leave me with one question:
Can the merge function be extended to support scripts interleaved
between blocks of non-code?
e.g. this works in
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 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
Hey guys!
This is one of my early community contributions. The server has an in tag mode
and a not in tag mode. The shebang both tells the OS where to find the
executable to run the script and sets enters tag mode. So:
#! /some/path
put the long date && the long time
?>FooBar
Should generate
Can’t answer regarding the design decision, but here is the pertinent line:
One recent feature that was introduced in LiveCode 6.6 was the ability to use
hashbangs (#! /path/to/livecode) in LiveCode server scripts instead of script
open and close tags ().
Of note is the “instead of” statement
