So is this issue officially fixed in ngspice 31-2? If so, we should close this bug report so we are one bug report closer to getting 5.1.5 released.
So is this issue officially fixed in ngspice 31-2? If so, we should close this bug report so we are one bug report closer to getting 5.1.5 released.