Note, if you get something like this: 2!:0 'echo $0' sh
You should try this: 2!:0 'which $0' /bin/sh And you can get the full shell environment using 2!:0 'set' (Which of course can be compared with the result of set run in the terminal.) (I was hoping to be able to explain how to run jqt under dtruss, or dtrace, to report what exactly J is executing, but osx system integrity protection makes that rather problematic. It may be that serious osx work nowadays requires at least two machines -- one being an osx implementation which has system integrity protection disabled (and, not connected to the internet) and the other being an internet connected machine (with some non-standard physical medium to transfer files between the machines). Or maybe just an osx machine which is completely recovered from backups rather frequently, to reduce the severity of infections from internet sources.) FYI, -- Raul On Sun, Oct 4, 2020 at 2:21 PM Thomas Bulka <[email protected]> wrote: > > Am 28.09.2020 21:07 schrieb Julian Fondren: > > If that still reveals no problems, maybe the terminal and J > > are using different shells? > > > > 2!:0 'echo $0' > > /bin/sh > > Hi Julian, > > that might be a hint in the right direction. I found out, that joxygen > works fine in jcon but gives the aforementioned errors in jqt. I'll keep > investigating... > > Regards, > > Thomas > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
