If your profile changes mean that jpath'~addons' give the wrong answer, then this is probably a bad situation.
Probably not urgent, but at some point you should rework your startup so that ~addons and friends work. Not sure, but I think the tools to make your mods to startup so that these other things work are available. On Sun, Nov 12, 2017 at 2:28 PM, J. Patrick Harrington <[email protected]> wrote: > OK, Thanks Eric. One last thing. I did start jconsole as you > suggested and then loaded the addons/ide/jhs/config/jcs.cfg file. > This does start the JHS server and open the browser tab at jijx. > > (I can't do load '~addons/ide/jhs/config/jcs.cfg' because in my > profile.ijs file, I load some definitions and change tie working > directory. Wonder if this is a problem?) > > I'll give it a rest for now and continue to us jqt. > > > On Sun, 12 Nov 2017, Eric Iverson wrote: > >> The jhs.cfg on 1 line should not make a difference so there is some other >> type at work there. >> >> Also if this change still opens the browser tab, then the AUTO value of 0 >> is not working as it should. >> >> Assuming the problem is with starting a terminal and my going on about >> AUTO >> was a red herring, you should go back to your original jhs.cfg. >> >> Then start a terminal window and do. >> >> ... $ j64-806/bin/jconsole >> load'~addons/ide/jhs/config/jcs.cfg' >> >> this should start your JHS server and open a browser tab at jijx. >> >> On Sun, Nov 12, 2017 at 1:54 PM, J. Patrick Harrington <[email protected] >> > >> wrote: >> >> >>> Here's another thing. In editing the jhs.cfg file, I had >>> put AUTO=: 0 on a seperate line after the PORT=: line. >>> I went back and changed that to >>> >>> PORT=: 65001[AUTO=:0 NB. serve port 65001 >>> >>> as in your message, and then running j64-806/bin/jhs >>> gives the J HTTP Server message and the browser opens >>> to jijx automatically. >>> >>> >>> On Sun, 12 Nov 2017, J. Patrick Harrington wrote: >>> >>> >>>> Well, I just tried that. Something peculiar that I had not seen >>>> before is that the jc (console) icon gives that same pop-up >>>> window with unable to find shell message. But, if I run >>>> ~/j64-806/bin/jconsole >>>> in any window, and then enter the sentences you gave me >>>> I get this message in that window: >>>> >>>> J HTTP Server - init OK >>>> >>>> Ctrl+c here signals an interrupt to J. >>>> >>>> Browse to: http://127.0.0.1:65001/jijx >>>> >>>> Then if I open the browser and go to jijx, >>>> jhs is there and running as it should. >>>> >>>> So it seems both the jc and jhs icons want a window they >>>> can't find. The jqt icon works just as before. >>>> >>>> On Sun, 12 Nov 2017, Eric Iverson wrote: >>>> >>>> Patrick, >>>>> Do not understand why AUTO=:0 in jhs.cfg doesn't work. >>>>> >>>>> Please try the following: >>>>> >>>>> close all browsers >>>>> >>>>> start jconsole and run the following sentences: >>>>> config_jhs_=: 3 : 'PORT=:65001[AUTO=:0' >>>>> load'~addons/ide/jhs/core.ijs' >>>>> init_jhs_'' >>>>> >>>>> This should start the JHS server and do nothing with the browser. >>>>> >>>>> Then start a browser and browse to jijx. >>>>> >>>>> Let me know what happens. >>>>> >>>>> >>>>> On Sun, Nov 12, 2017 at 12:48 PM, J. Patrick Harrington >>>>> <[email protected]> >>>>> wrote: >>>>> >>>>> > I went back and put in AUTO=: 0 >>>>> > Still get the same "Unable to find shell" popup. >>>>> > > > On Sun, 12 Nov 2017, Eric Iverson wrote: >>>>> > > > I think the jhs.cfg change for AUTO should work. Please try that >>>>> again > > and >>>>> > > check things. In your email you were setting AUTO to the letter O >>>>> and > > not >>>>> > > the digit zero. >>>>> > > > > On Sun, Nov 12, 2017 at 12:33 PM, Eric Iverson > > < >>>>> [email protected]> >>>>> > > wrote: >>>>> > > > > Sounds like a race condition. The JHS init is running the >>>>> browser to > > load >>>>> > > > the jijx page before JHS is ready to server the page. >>>>> > > > > > > I have never seen this before. Not sure how to coordiate >>>>> this > > > better, but >>>>> > > > will think about it. >>>>> > > > > > > For now, putting in AUTO=: 0 in the jhs.cfg file should >>>>> work > > > reasonable >>>>> > > > well. Just means you need to have the browser started manually >>>>> and > > > do the >>>>> > > > browse to the jijx page manually. A bookmark will make this >>>>> easier. >>>>> > > > > > > > > > > > > On Sun, Nov 12, 2017 at 12:22 PM, J. Patrick >>>>> Harrington < >>>>> > > > [email protected] >>>>> > > > > wrote: >>>>> > > > > > > Some progress. I've found that if I first start the >>>>> browser >>>>> and > > > click the >>>>> > > > > http://127.0.0.1:65001 link it says (of course) "Unable to > >>>>> > >>>>> > > connect". >>>>> > > > > Then >>>>> > > > > if I run j64-806/bin/jhs, a new tab in the browser opens, >>>>> running > > > > jhs. >>>>> > > > > The terminal window where I invoked j64-806/bin/jhs now says: >>>>> > > > > > > > > J HTTP Server - init OK >>>>> > > > > > > > > Ctrl+c here signals an interrupt to J. >>>>> > > > > > > > > Browse to: http://127.0.0.1:65001/jijx >>>>> > > > > > > > > But even if I have the browser running, the blue icon >>>>> will not > > > > start >>>>> > > > > jhs, but puts up a window with that "Unable to find a shell" >>>>> msg. >>>>> > > > > > > > > I see you have sent a few more messages; I see what >>>>> else I can > > > > learn. >>>>> > > > > > > > > Thanks, Patrick >>>>> > > > > > > > > > > > > On Sun, 12 Nov 2017, Eric Iverson wrote: >>>>> > > > > > > > > Sounds like the problem is when the JHS jconsole task >>>>> tries to > > > > start the >>>>> > > > > > browser. >>>>> > > > > > > > > > > First thing check is to see if the JHS jconsole >>>>> task has any >>>>> > > > > > interesting >>>>> > > > > > info (probably after you dismiss the popup). >>>>> > > > > > > > > > > There is a chance JHS started OK and the failure >>>>> is >>>>> just in > > > > > launching >>>>> > > > > > the >>>>> > > > > > browser. >>>>> > > > > > > > > > > Try starting your browser manually and then >>>>> browsing to >>>>> > > > > > localhost:65001/jijx and see if that gives you a JHS jijx > >>>>> > >>>>> > > > session. >>>>> > > > > > > > > > > > > > > > > > > > > On Sun, Nov 12, 2017 at 11:14 >>>>> AM, J. Patrick Harrington < >>>>> > > > > > [email protected]> >>>>> > > > > > wrote: >>>>> > > > > > > > > > > I recently downloaded the latest beta to my laptop >>>>> which >>>>> > > > > > > > > > > > is a Dell XPS running Ubuntu 16.04. No problems >>>>> with >>>>> > > > > > > jconsole and with installing jqt. Here is JVERSION: >>>>> > > > > > > JVERSION >>>>> > > > > > > Engine: j806/j64avx/linux >>>>> > > > > > > Beta-7: commercial/2017-10-26T15:44:00 >>>>> > > > > > > Library: 8.06.09 >>>>> > > > > > > Qt IDE: 1.6.1/5.3.2 >>>>> > > > > > > Platform: Linux 64 >>>>> > > > > > > Installer: J806 install >>>>> > > > > > > InstallPath: /home/tages/j64-806 >>>>> > > > > > > Contact: www.jsoftware.com >>>>> > > > > > > > > > > > > The problem is that when I try to start jhs, >>>>> either by >>>>> > > > > > > the jhs806 icon or by j64-806/bin/jhs, I get a pop-up >>>>> > > > > > > window that says "Unable to find a shell" and no >>>>> connection >>>>> > > > > > > to my browser (firefox). Any ideas about what the problem >>>>> > > > > > > might be? jhs worked fine on the earlier version of 806 >>>>> > > > > > > (which I've now overwritten) and still works (I just tried >>>>> > > > > > > it) on j64-805. >>>>> > > > > > > > > > > > > Thanks, Patrick >>>>> > > > > > > ------------------------------ >>>>> ------------------------------ >>>>> > > > > > > ---------- >>>>> > > > > > > For information about J forums see > > > > > > >>>>> http://www.jsoftware.com/forum >>>>> > > > > > > s.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 >>>>> > > > > > > > > > > > > > > ------------------------------ >>>>> ---------------------------------------- >>>>> > > For information about J forums see http://www.jsoftware.com/forum >>>>> s.htm >>>>> > > > ------------------------------------------------------------ >>>>> ---------- >>>>> > For information about J forums see http://www.jsoftware.com/forum >>>>> s.htm >>>>> > >>>>> ----------------------------------------------------------- >>>>> ----------- >>>>> For information about J forums see http://www.jsoftware.com/forum >>>>> s.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 >>> >>> ---------------------------------------------------------------------- >> 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
