There's several things going on here. (1) the ijx session persists, and you can interact with it from multiple browser windows (with a few quirks about how updates work when you've multiple windows open to the same session).
(2) Errors (which are requests to the server, such as typed in commands) go into that log. (I don't know enough about what you were doing to cause those error messages). (3) When you loaded the page from history, there's a chance that the javascript on the page didn't work right (which would prevent further interaction with the server). But a simple load of your ijx page url should fix that. (4) To empty your session, you would shut down the console window which represents the ijx server. Or, if jhs has been redone so that there's no window, try using the exit command... (with a '' argument). Thanks, -- Raul On Thu, Dec 5, 2019 at 2:25 PM 'Jim Russell' via Beta <[email protected]> wrote: > > In case anyone cares, this happened while I was going through : Primer > Script file > > which doesn’t matter, and of course this was lost when I poorly chose the Red > button to close the j ijx window. How should I have ended the current J > session, but kept the remainder of my Safari windows? > > > On Dec 5, 2019, at 2:14 PM, 'Jim Russell' via Beta <[email protected]> > > wrote: > > > > Not sure what I am seeing here… > > > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
