Fair point about emacs. I also recently discovered the jfiles addon, which will definitely help.
On Wed, Dec 30, 2015 at 8:22 PM, Devon McCormick <[email protected]> wrote: > Running J under emacs obviates all these session-losing problems. > On Dec 29, 2015 10:13 PM, "David Lambert" <[email protected]> wrote: > > > One might try setting process limits before starting j. Perhaps run j at > > low priority. > > When I expect I might consume all my RAM I try to watch the system > monitor > > so I can stop j before the system enters page fault hell. Sometimes this > > works. > > Once the page faulting starts there's no hope for finding jbreak. I can > > interrupt explicit code without losing the j console session, not so > with a > > tacit sentence. > > > > On 12/29/2015 09:23 PM, [email protected] wrote: > > > >> Date: Tue, 29 Dec 2015 21:19:00 -0500 > >> From: Alex Shroyer<[email protected]> > >> To:[email protected] > >> Subject: [Jprogramming] stopping a runaway process > >> Message-ID: > >> <CAK1S= > >> [email protected]> > >> Content-Type: text/plain; charset=UTF-8 > >> > >> Is there a way to make it so Ctrl+C always interrupts the interpreter > >> and/or stops the currently running J sentence? > >> > >> Sometimes I will be working on a sentence interactively, do something > >> dumb, > >> which results in having to kill the process, losing any unsaved state. > >> It'd be nice if there was a way to back out of a runaway process more > >> gracefully. > >> > > > > ---------------------------------------------------------------------- > > 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
