MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
105 bytes added ,  12 October 2024
no edit summary
No edit summary
No edit summary
Line 118: Line 118:
     Aside from the modification for the MCP machine model, it is otherwise just zsh however the following (mode) commands are available to establish different shell behaviour in support of the KEE:
     Aside from the modification for the MCP machine model, it is otherwise just zsh however the following (mode) commands are available to establish different shell behaviour 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>shhs</b></li><li><b>upsh</b></li></ul>
     which have the lisp, haskell, and prolog natures, respectively. Lisp and prolog implementations can vary but shcl and upsh require sbcl and swipl, respectively.
     which have the lisp, haskell, and prolog natures, respectively. <b>shhs</a> is a wrapper for HsShellScript, the others are named from the external source projects, q.v. Lisp and prolog implementations can vary but shcl and upsh require sbcl and swipl, respectively.
   <b>mcpcms</b> can be accessed with ssh using the following script. Using the FQDSAgentName syntax is equivalent to what the launch link does in an AKPERSONs session.<pre><tt>#!/usr/bin/bash
   <b>mcpcms</b> can be accessed with ssh using the following script. Using the FQDSAgentName syntax is equivalent to what the launch link does in an AKPERSONs session.<pre><tt>#!/usr/bin/bash
# save as &lt;fileName&gt; and invoke with &lt;fileName&gt;  &lt;connect-spec&gt; where             
# save as &lt;fileName&gt; and invoke with &lt;fileName&gt;  &lt;connect-spec&gt; where             

Navigation menu