On 8/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > good catch, you can debug remotely on my computer :) > yes, william, you are right: the small examples work but not the big > ones. i didn t anticipate that SAGE was using files behind the scenes > (i don't know anything about how that works). > in any case, the fact that sage uses scp is not really a problem. this > is another workaround: > ssh -t tunnel scp test_file remote:~/test_file > (after setting all the passwordless stuff) > so if that s all that s needed, maybe one could add to the server > option of the interface a prefix and a suffix to trail the scp command > with, and the same for the ssh (or rsh or whatever is used)
You could try implementing this. Take a look at SAGE_ROOT/devel/sage/sage/interfaces/expect.py and SAGE_ROOT/devel/sage/sage/interfaces/mathematica.py Do a text search for "scp" in there. Make changes and do "sage -br" to start SAGE with the changes in effect. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
