Thanks to Roger Eller and Mike Bonner - shell is a function! Of course it is,
it says so in the LS documentation, even though the examples don't show it
embedded in a function-using script.
I got it wrong because I didn't read the docs closely enough - I imagined that
it was a handler that act
thanks guys. Phil's snippet in the archives was educational:
There are always variations of unix commands that will do what one wants.
sqb
On 29 October 2011 12:11, Phil Davis wrote:
> You can get the Shell Command Help plugin from Rev Online. I use it almost
> every day. :-)
>
> Phil
>
>
>
>
You can get the Shell Command Help plugin from Rev Online. I use it almost every
day. :-)
Phil
On 10/29/11 11:53 AM, Warren Samples wrote:
On 10/29/2011 12:59 PM, stephen barncard wrote:
on a side note regarding shell - I just ran this from the message box:
put shell("man zip")
and got
On 10/29/2011 12:59 PM, stephen barncard wrote:
on a side note regarding shell - I just ran this from the message box:
put shell("man zip")
and got this text:
Not an answer to your question, but that doesn't happen here running Linux.
Here is something from discussion of Phil Davis' Shell
on a side note regarding shell - I just ran this from the message box:
put shell("man zip")
and got this text:
(clip)
ZIP(1L)
ZIP(1L)
NNAAMMEE
zip - package and compress (archive) files
SSYYNNOOPPSSIISS
zziipp
[
Ah k yep. the double dash help is a pretty common unix'y thing, haven't used
IM to convert and no mac so couldn't test. Thx for clarifying!
On Sat, Oct 29, 2011 at 9:34 AM, Warren Samples wrote:
> On 10/29/2011 09:40 AM, Graham Samuel wrote:
>
> shell(/opt/local/bin/convert)
>>
>
> Mike's res
On 10/29/2011 09:40 AM, Graham Samuel wrote:
shell(/opt/local/bin/convert)
Mike's response contains all the correct information, but it can be
distilled to this:
change what you what you type into the message box to:
put shell("/opt/local/bin/convert")
This should display in the messa
On Sat, Oct 29, 2011 at 10:40 AM, Graham Samuel wrote:
> Thanks to all who replied.
>
> in Terminal, and got:
>
> /opt/local/bin/convert
>
> I don't exactly know what 'opt' is, but I can open /opt/local/bin/ in the
> Mac Finder, so it exists OK, and it contains a file 'convert' as expected.
> Any
Wasn't real clear there.. Yes shell is a function, but livecode uses subtle
clues to interpret what is what. So a function on a line by itself with no
way to handle the output is instead seen as a handler because the engine is
making its best guess. And since there is no handler named shell() you
shell is a function, you have to actually do something with what is
returned.
notice if you do the following from the message box:
shell() with nothing, you get handler not found
If you do this instead
put shell() you get bad parameter because you didn't give the function
anything to work with.
Thanks to all who replied.
Just a brief reminder that I found I could invoke ImageMagick from Terminal on
my Mac, but not via 'shell' within an LC program on the same machine.
I really hoped that Andre's insight was right and that it was a path issue -
really because I understand what one of th
On 10/28/2011 03:09 PM, Andre Garzia wrote:
Try this on your terminal:
which convert
This will return the path to the convert command, in my case is:
/usr/local/bin/convert
So change your convert command in the shell to "/usr/local/bin/convert
image.jpg blabla" and see if you can get it to wo
Graham,
This is probably a PATH issue. See when you launch your terminal, a bash
script is executed. You can think of this script as the code in
preOpenTerminal. Among other things, this script will set the PATH variable
which holds a list of folders to look for commands in. So when you use the
"c
On 10/28/2011 12:53 PM, Bob Sneidar wrote:
Is this in Windows or Mac? Im Mac to get usage for a shell command you have to
preface it with man. I think it's short for manual. This only works if whatever
installed the command in the shell also installed a man page.
Bob
Technically you are cor
Is this in Windows or Mac? Im Mac to get usage for a shell command you have to
preface it with man. I think it's short for manual. This only works if whatever
installed the command in the shell also installed a man page.
Bob
On Oct 28, 2011, at 7:06 AM, Warren Samples wrote:
> On 10/28/2011
On 10/28/2011 11:52 AM, Graham Samuel wrote:
While trying to get just a bit comfortable with a command-line interface, I
started Terminal on Mac OSX Lion and eventually got a command to work (after
finding out how to cope with spaces in file and folder names). I put the same
thing in an LC 'sh
On 10/28/2011 11:52 AM, Graham Samuel wrote:
While trying to get just a bit comfortable with a command-line interface, I
started Terminal on Mac OSX Lion and eventually got a command to work (after
finding out how to cope with spaces in file and folder names). I put the same
thing in an LC 'sh
While trying to get just a bit comfortable with a command-line interface, I
started Terminal on Mac OSX Lion and eventually got a command to work (after
finding out how to cope with spaces in file and folder names). I put the same
thing in an LC 'shell' command and got a runtime error (Handler:
18 matches
Mail list logo
