MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 121: Line 121:
     Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke <b>cande</b>.
     Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke <b>cande</b>.
     Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates are available to establish different shell behaviours in support of the KEE:
     Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates are available to establish different shell behaviours in support of the KEE:
     <ul><li><b>shcl</b> </li><li><b>shhs</b></li><li><b>upsh</b></li></ul>
     <ul><li><b>shcl</b> </li><li><b>CANDE HSH</b></li><li><b>upsh</b></li></ul>
     which have the lisp, haskell, and prolog natures, respectively. <b>shcl</b> is the only one which is a full shell run at the ODT command level like <b>cande</b>, the others are ways
     which have the lisp, haskell, and prolog natures, respectively. <b>shcl</b> is the only one which is a full shell run at the ODT command level like <b>cande</b>, the others are ways
     to do posix shell things in lang and are run as commands in cande/zsh. While in general Lisp and Prolog implementations can vary in the Boot KEE, these lang shells are integral with
     to do posix shell things in lang and are run as commands in cande/zsh. While in general Lisp and Prolog implementations can vary in the Boot KEE, these lang shells are integral with