Christopher Jefferson

I will admit I'd never looked at LoadPackage, and I assumed it just recursively called `LoadPackage`. After reading the source, I see that as @stevelinton says, it is more complicated...

Here is one option, which doesn't add too much code. In short, use the existing `PackageAvailabilityInfo` and `TestPackageAvailability` functionality, when `LoadPackage` is called interactively, with `banner=true` (so we know users...

Might want to edit the output under `SetInfoLevel(InfoPackageLoading, PACKAGE_INFO);` so it reads more naturally, but that could be done for other situations too. Perhaps something like: ``` gap> LoadPackage("profiling"); #I...

@fingolfin : I was planning that there will be no output if there is no error. My current way to do that is to basically double the work -- only...

I believe `SetPrintFormattingStatus` always worked, except for `*stdout*` was it has been broken (at least sometimes). Personally, I've never seen a good reason to disable indentation, so I'd be happy...

Swapping master pointers doesn't help, as once a thread has looked at a permutation and found it's a perm4, it will continue treating it like one, something like: ``` Thread...

Seperate from @markuspf wanting a callback, we could extend/rename `--quit-on-break` to also cover syntax errors.

Hi, I have a few questions (I'd go through these in order, there is no point answering '3', if it turns out '1' means we don't really want the function...

Just a suggestion -- I've found myself increasingly just using records (for example, I put functions in vole into a record called `Vole`, like `Vole.Stabilizer`). Everything seems to work fine...

I am tempted to forbid it, because I find it hard to imagine someone is using this on purpose, and hasn't just made a typo and is confusing themselves.