I have axiom-3.9 and texmacs-1.0.6 installed. When I open an axiom session inside TeXmacs, the session starts up and captures the axiom *inputs*. However, the results of the session are invisible. I haven't tried this from upstream sources yet to see if it's Gentoo-specific.
Apparently this is Gentoo-specific and not upstream. I rebuilt both TeXmacs 1.0.6 and Axiom 3.9 from upstream source and the output from an Axiom session shows up just fine in a TeXmacs document. I'm going to try a few other things to see if it's something simple, like a missing environment variable in /etc/env.d.
Since you managed to get it working by compiling it yourself, could you try to locate which of the two, axiom or texmacs (or both), that contains the problem: So try to use your own built axiom with the gentoo's texmacs and the other way around. Report back here with your results.
OK ... did half of it. Using the Portage texmacs-1.0.6 with Axiom 3.9 from the Axiom web site works just fine! So this looks like an Axiom problem, not a TeXmacs problem at first glance. Axiom's build process, which it resembles the standard "configure; make; make install" pattern, is decidedly different in implementation. After the configure, you have to set some environment variables, and the "make install" needs some arguments if you want to put it anywhere but the default, which is way down somewhere in the /usr/local tree. There may be some upstream bugs if you don't accept that default; I had a few mysterious problems when I tried to do a make install exactly where I wanted Axiom to end up. And I also think something needs to be added to /etc/env.d for the Axiom path; when I ran make install it asked me to add an entry to PATH, specifically PATH=/usr/local/axiom/mnt/linux/bin That's in my local file 99znmeb in /etc/env.d ... I haven't looked at the Axiom ebuild to see whether that happens during the Gentoo install.
This seems like an Axiom problem, but it would be nice if you could try the other way around so that we are sure.
No response, so my guess is that this is an axiom problem. Reassigning to maintainer of axiom and CCing text-markup.
This is an Axiom problem but I think it's an upstream issue. Can you please try the axiom-9999 ebuild and see if you can reproduce it, maybe this is now fixed? I've noticed this myself as well and others have made similar comments [1] on the Axiom wiki. [1] http://wiki.axiom-developer.org/TeXmacs
Ok, fixed in CVS, the problem was in the wrapper scripts. If you emerge sync and remerge -r1 the issue with TeXmacs should go away. Thanks!
