Re: Applescript & the CLI
Re: Applescript & the CLI
- Subject: Re: Applescript & the CLI
- From: Phi Sanders <email@hidden>
- Date: Mon, 5 Feb 2001 14:25:23 -0500
1) I think Emmanuel was referring to the worksheet functionality
that Smile already has (and tho' I use Script Debugger mostly,
I like Smile worksheets for testing pieces of code...)
2) I was wondering if (similar to file drops) AppleScript in os X
could implement command-line invocation by requiring a specific handler :
on commandLine(args)
--args would be a list or record of the command line arguments
end commandLine
By implementing this Scripters could fork their process to
behave differntly when run from the command line...
barring that, can we get some kind of global (to the script) flag
indicating how it was invoked???
Without it, scripts couldn't <shouldn't?> accept CLI invocation
~Phi
--
Phi Sanders
"And now, back to your regularly scheduled reality."
On 2/3/01, Joshua Whalen {email@hidden} said the following :
>
> Sorry for asking the obvious if I do, but does "an OSA Shell" mean, a
>
> window with a pop-up which lets you choose the OSA language (like Script
>
> Editor), where you can enter text, and where the "Enter" key executes the
>
> selected line of block of lines ?
>
>
What a really cool idea! No, actually, I guess what I meant was just a
>
an applescript/raw apple event aware cli. But your idea is actually much
>
better. I don't think it should be a pop-up. I'd like something that
>
would let me telnet in from some poor, benighted souls windows box and
>
run applescript or frontier or whatever. I guess the way to implement
>
that would be to have a script (or text file) like the csh has it's
>
.profile file, and that would implement a default language. Then, of
>
course, you choose a different one at run time by doing something like
>
"set env OSALang -l Usertalk". The idea is basically to be able to run
>
applescript or usertalk or whatever from a remote shell, or from a
>
crontab when no one is logged in on the console. The shell syntax should
>
allow some traditional unix tings like the set env directive, since
>
that's how shells do things, and a mac'n'unix (pronounced like
>
frank'n'stein) geek like me should be able to use this as their default
>
shell wit!
>
hout loss of functionality, one way or the other.
>
>
I know a lot of people aren't crazy about the fusion of macintosh and
>
BSD, but as long as that's where it's going, we may as well think about
>
where we would like to put the glue, and see what we can do about
>
putting it where we want it. I think spec'ing out a Mac Shell would be a
>
worthy development project.
>
>
One more feature of the Mac Shell should be, of course, recordability
>
and editability of a session. There should be an environment variable
>
"save session as script" like "set env record script" to save as a
>
compiled script, or "set env record applet" to save as an executable applet.
>
>
Thanks for indulging me!
>
>
>
Joshua
>
>
>
>
>
>
>
> TIA
>
> Emmanuel
>
> _______________________________________________
>
> applescript-users mailing list
>
> email@hidden
>
> http://www.lists.apple.com/mailman/listinfo/applescript-users
>
>
>
>
>
>
=====================================
>
=====================================
>
==========================================================================
>
There are running processes. Why don't we go chase them?
>
=====================================
>
=====================================
>
==========================================================================
>
_______________________________________________
>
applescript-users mailing list
>
email@hidden
>
http://www.lists.apple.com/mailman/listinfo/applescript-users