Can you confirm that this bug is no longer present in the 5.44.0 release
of Maxima, please?

Leo
(current upstream maintainer of imaxima)

Reply via email to