Wow this was fast: 16h from the first report untill a positively revied
bugfix!
Thanks!!!
Am Freitag, 14. Februar 2014 01:36:27 UTC+1 schrieb Volker Braun:
>
> Fix is at http://trac.sagemath.org/15819 (needs review)
>
--
You received this message because you are subscribed to the Google Groups
Fix is at http://trac.sagemath.org/15819 (needs review)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this gr
The CommandLineHistory variable seems to only exists in gap-4.7+ which I
happened to have around. The gap version we ship also keeps a history, but
does not make the global variable available.
The history can be set to a fixed maximal length (say, 3) with
SetUserPreference("HistoryMaxLines
The problem with Tobias' memory leak in the GAP interface seems to be that
GAP keeps a log of all interactive commands in the undocumented variable
"CommandLineHistory". This quickly fills up the available RAM if things are
done in a tight loop:
sage: G = DihedralGroup(6)
sage: tbl = G.characte
