On Sat, Sep 19, 2009 at 1:43 AM, William Stein <[email protected]> wrote: > On Sat, Sep 19, 2009 at 1:34 AM, Simon King <[email protected]> wrote: >> >> Next problem: >> >> The log file that is created when I put gap=Gap(logfile="logfile") >> contains symbols that can't be interpreted by GAP. Hence, Read >> ("logfile"); in GAP won't work: >> >> @iRead("/home/king/SAGE/sage-4.1/local/pGroupCohomology/GapMaxels"); >> Read("/home/king/SAGE/sage-4.1/local/pGroupCohomology/GapMaxels");^M >> @rRead("/home/king/SAGE/sage-4.1/local/pGroupCohomology/ >> GapMaxels");@j...@ngap> @iRead("/home/king/SAGE/sage-4.1/local/ >> pGroupCohomology/GapMB"); >> >> Where does all this @i and @r come from? I thought that the purpose of >> the logfile is to get executable GAP code, so that one can do >> debugging. > > 1. Those control characters are there because GAP is put in a special > "control" mode when Sage communicates with it. See the command used > to start GAP. > > 2. Regarding what the logfile option is for, well.. it is just > something built into pexpect. There are is certainly no guarantee > that it can be used to exactly reproduce a session for debugging. >
It occurred to me that GAP does have a "workspace" save feature, which might be useful. It makes it possible to save the complete state of GAP. Maybe you can use sage to get GAP into some state of interest to you, then save the workspace, then load it into another GAP session and interact with it. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] 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://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
