OK, it apparently was a bug of the previous version of msolve: For `msolve -P 2 -f file.ms` with msolve 0.6.5-2 yields the wrong result claiming that the dimension is positive, no matter whether file.ms ends with a newline character or or not, while msolve 0.6.6-1 yields the correct result in both cases. Still, from within Sage, I get the wrong result. So I guess I need to force Sage to use the system msolve rather the one which Sage built during installation.
-- Peter Mueller Marc Mezzarobba schrieb am Sonntag, 30. Juni 2024 um 12:27:25 UTC+2: > 'Peter Mueller' via sage-devel wrote: > > I guess that in your snippet, you manually typed the `enter` key after > > the `cat` command in the console. > > Hmm, no, there is a newline at the end: > > ~$ hexdump -c /tmp/tmprcz_zw9l > 0000000 a , b \n 2 \n a ^ 2 + a , \n b ^ 2 > 0000010 + b \n > 0000013 > > -- > Marc > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/848baa32-eb93-4bd7-9b7f-b3b06901b5c8n%40googlegroups.com.
