I found that c code. It is for a server-socket and client-socket.
Two separate programs which we could call from live code
with a shell command and give arguments if needed.
JB
> On Dec 18, 2019, at 12:56 PM, doc hawk via use-livecode
> wrote:
>
>
> On Dec 18, 2019, at 12:51 PM, JB via
On Dec 18, 2019, at 1:24 PM, JB via use-livecode
wrote:
>
> Thank you very much!
>
You’re quite welcome.
> I will be playing around with these a lot.
>
I’m interested to see what you do with it.
Also, at the conference this year, I asked panagiotis, who bounced me to Mark
on the
Thank you very much!
I will be playing around with these a lot.
JB
> On Dec 18, 2019, at 1:20 PM, doc hawk via use-livecode
> wrote:
>
>
> On Dec 18, 2019, at 1:03 PM, JB via use-livecode
> wrote:
>>
>> Actually as I said in the first post I do not really need it. I was
>> reading the
On Dec 18, 2019, at 1:03 PM, JB via use-livecode
wrote:
>
> Actually as I said in the first post I do not really need it. I was
> reading the manual about something else which I have already
> forgot and I ran across the code so I tried it.
Investigate “sockets” in the dictionary.
>
> But
Actually as I said in the first post I do not really need it. I was
reading the manual about something else which I have already
forgot and I ran across the code so I tried it.
But I am interested in messing around with writing to another
application if you have any examples. Also if you needed
On Dec 18, 2019, at 12:51 PM, JB via use-livecode
wrote:
>
> A year or so ago I was messing around with the terminal in c code
> and found some code that opens two terminals and they talk to
> each other.
>
> Is that something I can use to communicate with live code too?
Conceivably, but
A year or so ago I was messing around with the terminal in c code
and found some code that opens two terminals and they talk to
each other.
Is that something I can use to communicate with live code too?
JB
> On Dec 18, 2019, at 12:47 PM, doc hawk via use-livecode
> wrote:
>
>
> On Dec 18,
On Dec 18, 2019, at 12:38 PM, JB via use-livecode
wrote:
>
> open process "/Applications/Utilities/Terminal.app" for write
> write tMessage && the long time & return to stdout
*That* is the problem.
If you open a terminal from within livecode, that doesn’t turn it into stdout,
which already
9:24 AM, Mark Wieder via use-livecode
> wrote:
>
> On 12/18/19 7:01 AM, JB via use-livecode wrote:
>> This isn’t something I need but I read in a older manual
>> you can write to the terminal using stdout. It said the
>> terminal needs to be open and you use code l
I really don’t use the shell or terminal much. When you
say it is awkward I suspect I did not do it right. All I did
was open the terminal and use open with the path and
it opened live code. Should I have written something
else? Am I supposed to launch a process?
JB
> On Dec 18, 2019, at
On Dec 18, 2019, at 11:06 AM, Bob Sneidar via use-livecode
wrote:
>
> Well, sudo already offers a mechanism to prevent volatile teminal activity.
But that’s a privilege restriction about superuser.
Generally, I would think that a process shouldn’t be able to write to a random
other
On 12/18/19 9:49 AM, JB via use-livecode wrote:
Well I tried it on OS X 10.11 using Livecode 4.6.2
and the application launches then I create a new
main stack and use the message box to enter
your code and nothing happens.
I don't have anything that old to test with, but it works with OSX
Well, sudo already offers a mechanism to prevent volatile teminal activity.
Bob S
> On Dec 18, 2019, at 11:02 , doc hawk via use-livecode
> wrote:
>
>> I didn’t know you needed to launch it from
>> the command line.
>
> Without that, I don’t think that livecode could be associated with any
On Dec 18, 2019, at 9:36 AM, JB via use-livecode
wrote:
>
> I didn’t know you needed to launch it from
> the command line.
Without that, I don’t think that livecode could be associated with any
particular terminal.
In fact, I suspect that OSX would block any attempt from any non-descendent
use-livecode wrote:
>> This isn’t something I need but I read in a older manual
>> you can write to the terminal using stdout. It said the
>> terminal needs to be open and you use code like
>> below to log or write to the terminal;
>> put "Hello world." into
I didn’t know you needed to launch it from
the command line.
Thanks,
JB
> On Dec 18, 2019, at 9:24 AM, Mark Wieder via use-livecode
> wrote:
>
> On 12/18/19 7:01 AM, JB via use-livecode wrote:
>> This isn’t something I need but I read in a older manual
>> you can wri
On 12/18/19 7:01 AM, JB via use-livecode wrote:
This isn’t something I need but I read in a older manual
you can write to the terminal using stdout. It said the
terminal needs to be open and you use code like
below to log or write to the terminal;
put "Hello world." into tMes
This isn’t something I need but I read in a older manual
you can write to the terminal using stdout. It said the
terminal needs to be open and you use code like
below to log or write to the terminal;
put "Hello world." into tMessage
write tMessage && the long time & return
18 matches
Mail list logo
