![\"2014-12-10](\"http:\/\/livecode.com\/wp-content\/uploads\/2014\/12\/2014-12-10-11_55_44-MTPuTTY-Multi-Tabbed-PuTTY.png\")
<\/a><\/p>\nClick to Zoom<\/em><\/p>\n After some time, I had produced a script which operates as a simple shell type interface. But how does it work? It\u2019s actually fairly simple. The script is a LiveCode Server script, designed to be invoked via command line. When it starts up, it reads in the options passed to it on the command line to determine how it should behave. The options passed to it are in the $x variables, starting at $0. $# tells us how many were passed.<\/p>\n #!\/usr\/local\/bin\/livecode-server ## array for storing the options passed to this program ## load options \u00a0There are currently two modes: interactive and execute. We can also pass the -p option to tell it to expect data to be piped to it, and read it into a variable called \u2018input\u2019. If we pass it the -e option it starts up in execute mode, and expects you to have specified a command for it to run. It then exits after running the command. Usage for this would be like \u201clcsh -e \u2018put hello world\u2019\u201d. Otherwise, it starts up in interactive mode.<\/p>\n ## read from pipe ## get command from last command line option and execute it, then quit ## interactive mode Execute mode simply takes the last command line option and uses do on it, then quits. Interactive mode reads 1 line from stdin at a time (i.e. it reads 1 typed line by the user at a time) and then determines what should be done with it. It uses the isCommand function to check the $PATH environment variable (which contains all of the directories which should be looked in for executable programs) to see if what was entered was a utility that is already installed, such as the standard Linux utilities. If it was, it uses shell() to execute the entered command. Otherwise, it uses the do command to execute it as normal LiveCode code, catching any generated errors so that they can be displayed without causing the program to exit:<\/p>\n ## checks to see if the first word is a command in $PATH There is also the optEnabled function that was referenced above. This checks to see if the program was loaded with a specific option enabled:<\/p>\n function optEnabled pOpt \u00a0This is quite clunky and has many, many problems – for example, there\u2019s no ability to pipe the output of some LiveCode to another program in interactive mode, and you can\u2019t open another program that requires interaction. However, I think that with a lot more work, this could become quite a robust and useful tool. It already provides some very handy functionality in it\u2019s current state, namely that I can pipe to it for text parsing:<\/p>\n
## substitute this with the path to your livecode server executable<\/span><\/p>\n
local sOpts<\/span><\/p>\n
repeat with x = 0 to ($# – 1)
<\/span>\u00a0 \u00a0 \u00a0 \u00a0do “put $” & x && “into tReadOpt”
<\/span>\u00a0 \u00a0 \u00a0 \u00a0if char 1 of tReadOpt is “-” then
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 repeat with y = 2 to the number of chars in tReadOpt
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0put char y of tReadOpt into sOpts[(the number of lines in the keys of sOpts + 1)]
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0end repeat
<\/span>\u00a0 \u00a0 \u00a0 \u00a0else
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 put tReadOpt into sOpts[(the number of lines in the keys of sOpts + 1)]
<\/span>\u00a0 \u00a0 \u00a0 end if
<\/span>end repeat<\/span><\/p>\n<\/div>\n
if optEnabled(“p”) then
<\/span>\u00a0 \u00a0 \u00a0 \u00a0read from stdin until EOF
<\/span>\u00a0 \u00a0 \u00a0 \u00a0put it into input
<\/span>end if<\/span><\/p>\n
if optEnabled(“e”) then
<\/span>\u00a0 \u00a0 \u00a0 \u00a0do sOpts[(the number of lines in the keys of sOpts)]
<\/span>\u00a0 \u00a0 \u00a0 \u00a0put return
<\/span>\u00a0 \u00a0 \u00a0 \u00a0quit
<\/span>end if<\/span><\/p>\n
repeat
\u00a0 \u00a0 \u00a0 \u00a0put “lcsh[” & the folder & “]# “
<\/span>\u00a0 \u00a0 \u00a0 \u00a0read from stdin for 1 line
<\/span>\u00a0 \u00a0 \u00a0 \u00a0put it into tCommand
<\/span>\u00a0 \u00a0 \u00a0 if isCommand(tCommand) then
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0put shell(tCommand)
<\/span>\u00a0 \u00a0 \u00a0 else
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 try
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0do tCommand
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0catch pError
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 put “Error:” & return
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 put pError
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0end try
<\/span>\u00a0 \u00a0 \u00a0 \u00a0end if
<\/span>\u00a0<\/span>\u00a0 \u00a0 put return
<\/span>end repeat\u00a0<\/p>\n<\/div>\n
function isCommand pCommand
\u00a0 \u00a0 \u00a0 \u00a0set the itemDel to “:”
<\/span>\u00a0 \u00a0 \u00a0 \u00a0put the folder into tFolder
<\/span>\u00a0 \u00a0 \u00a0 \u00a0put false into tIsCommand
<\/span>\u00a0 \u00a0 \u00a0 \u00a0repeat for each item tDir in $PATH
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0set the folder to tDir
<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0if word 1 of pCommand is among the lines of the files then put true into tIsCommand
<\/span>\u00a0 \u00a0 \u00a0 \u00a0end repeat
<\/span>\u00a0 \u00a0 \u00a0 \u00a0set the folder to tFolder
<\/span>\u00a0 \u00a0 \u00a0 \u00a0return tIsCommand
end isCommand<\/p>\n<\/div>\n
\u00a0 \u00a0 \u00a0 \u00a0repeat for each key tKey in sOpts
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0if sOpts[tKey] is pOpt then return true
<\/span>\u00a0 \u00a0 \u00a0 \u00a0end repeat
<\/span>\u00a0 \u00a0 \u00a0 \u00a0return false
<\/span>end optEnabled<\/span><\/p>\n<\/div>\n