Paul Zinn-Justin

neither of the first two lines do anything. I don't understand this submodule mess.

is there something wrong with my configuration? here's my .git/config ``` [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = [email protected]:pzinn/M2.git fetch...

what I ended up doing, for reference: instead of resetting the submodules to the current development branches (which has changes compared to when I started this PR) I ended up...

Note that it's not so easy to use `memoize` with say a method with options, as I think I pointed out in some other thread. e.g., givin ``` f= method(Options=>new...

oh, is it a factory bug?

#3499 provides a partial fix (no more segfault, just an error), though it would be better if it returned something like `({},id_R)`. Unrelatedly, note the rather cryptic error message ```...

> Other observation: if I comment out these lines: > > https://github.com/Macaulay2/M2/blob/ec9e9ac60ed4a8e791448942202f077a88a87e15/M2/Macaulay2/m2/debugging.m2#L15-L18 > > > then everything works fine: > ```m2 > i4 : blah 12 > ../../m2/debugging.m2:6:17:(1): error: debug...

Interestingly, the same test you propose at the top produces a quite different result on Macaulay2Web, which incorporates some major changes I made to the error workflow. I'll try to...

All I can add (a bit late) is that I think I'd effectively solved the problem on my branch (without any need to revert #3544), see attached screenshot. But as...

it looks like it's intentional (cf the argument `returnLastvalue` of `readeval`). but I don't understand why, superficially it seems like a bug.