Thanks Raul From the launch command: ------- Last login: Fri Dec 6 13:00:44 on ttys000 /Users/jamesrussell/j901-user/temp/launch.command ; exit; jamesrussell@Jamess-Mac-mini ~ % /Users/jamesrussell/j901-user/temp/launch.command ; exit;
J HTTP Server - init OK Ctrl+c here signals an interrupt to J. Browse to: http://127.0.0.1:65001/jijx ps ps -a man ps chsh -s /bin/zsh^C^Cxx ------- Ctrl-c is at least printed ^C (like other things, printed but ignored); Cmd-c is not printed, but rings a bell, and (I was about to say) neither exited the ijx server, but as I was composing this, i looked and was told “server busy event ignored” and”Your JHS Server has exited…”. So you are correct, although I don’t know which ^C did the deed. I wonder if the parting “;exit” command is what keeps other commands (ps, man,…) from being executed? (think I default to ksh) > On Dec 6, 2019, at 1:58 PM, Raul Miller <[email protected]> wrote: > > It's control-c in that command window, not cmd-c -- even on osx, but > it seems like you have to hit it several times before it takes effect. > > Thanks, > > -- > Raul > > On Fri, Dec 6, 2019 at 12:57 PM 'Jim Russell' via Beta > <[email protected]> wrote: >> >> I understand the documentation to say that the console launch window should >> remain active and available, for things like cmd-c after launch. It seems >> that is no longer correct, cmd-c, man command, etc are not processed after >> JHS starts, as near as I can tell. Should they be? >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
