Thank you for the detailed analysis. On Fri, 16 Oct 2020 12:25:53 -0400 John Scott <jsc...@posteo.net> wrote: > On Friday, October 16, 2020 11:29:14 AM EDT Jan Kriho wrote: > > The launcher scripts is dependent on sage-env binary which sets env for > > executing further commands > Note that even if sage-env were to be available, I don't think Cantor would be > able to find it. It appears to invoke `sage --root` to figure out where to > look, > but the output is empty.
I see, so the sage-env binary won't be called anyway. > Cantor could be doing things in a more clean way regardless though. Instead of > fiddling with $SAGE_ROOT in a shell script, it could use the one-liner > sage --ipython3 -i --simple-prompt > > or use /usr/bin/sage --sh for the shebang in the script and call sage-ipython This actually looks like a way better option. I have made a quick test with it, and it looks like it works like it's supposed to. Should the bug be reassigned to Cantor upstream?