Updates manual to version 5.49.0.
Put back the nref macros
Add some xrefs and TeX-style math for html and pdf
Fix math display of sinc definition
New function sinc
Merge branch 'master' into rtoy-highlightjs-example-maxima-blocks-texi-dev
Check that makeinfo version is > 5.1
Package amatrix: rework find_runs_nontrivial (called from ranks) to call accumulate,
Function accumulate: optional initial value may be 'false'.
Function accumulate: cut out commented-out code for handling matrix input.
New function accumulate to return partial results of applying a function to successive elements of a list.
In GENERIC-AUTOLOAD and LOADFILE, bind *PRINT-BASE* to 10 decimal as well as *READ-BASE*.
In functions oddp and evenp, put in an extra case for the argument being an atom
In package affine, cut out undocumented function pb,
rk_adaptive: add a (still undocumented) parameter that creates a debug file
wrstcse: Added functions for handling the min and the max values, only
The problem seems to be caused by removing property 'translate from 'mcond (in boolsimp.lisp) and then compiling a routine with return inside a conditional. Maxima branch_5_49_base_100_g7075cc379 https://maxima.sourceforge.io using Lisp SBCL 2.5.11 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (%i1) :lisp(remprop 'mcond 'translate) (TRANSLATE #<FUNCTION (LAMBDA (FORM) :IN "/home/gildea/src/maxima/src/transl.lisp")...
The docstring says it should be an integer. And it also says -1 means all integers are expanded. So should it really accept any real number? I did notice that factlim:3.0 works (with HEAD), but then double_factorial(6) returns 48.00000...1. But with the default factlim value of 100000, double_factorial returns 48. Not sure what's going with that, but that's probably a different issue from this one. Easy enough to add a :setting-predicate for factlim to make sure it's a real (or integer) so that it...
non numeric value for factlim
User documentation: Function: genfact (x, y, z) Returns the generalized factorial, defined as x (x-z) (x - 2 z) ... (x - (y - 1) z). Thus, when x is an integer, genfact (x, x, 1) = x! and genfact (x, x/2, 2) = x!!. From the source code, it's clear the intent is for the second argument to be rounded down to the next integer (floor)--otherwise we'd have a product from 0 thru a half integer for the !! case. I'll look at double_factorial.
apply1 sets match to zero when instead the replacement is zero.
Thank you for the bug report. I have confirmed that the bug exists in Maxima 5.47 and it appears to have been fixed before 5.48. Can you try again with a more recent version of Maxima, either 5.48 or, preferably, 5.49, the most recent version?
Incorrect integration leads to incorrect series in fourie package
Dear Devin Greene, In case you are interested, our package pdefourier solves this problem and many other potential problems when the input contains trigonometric expressions or a product of a polynomial and a trigonometric expression https://github.com/emmanuelroque/pdefourier I hope you find it helpful. There is also an arxiv preprint where we explain why even Mathematica has many issues regarding Fourier series. https://arxiv.org/abs/2004.02604 Best, Emmanuel
numeric evaluation of genfact
For the record, the source code for genfact in src/asum.lisp shows that it simplifies only for first and last arguments which are fixnums, and second argument such that floor yields a fixnum. Probably the documentation should mention that. I didn't find any description of what genfact is supposed to implement, exactly. I don't see any statements in the code and a web search for "generalized factorial" doesn't seem to find anything. I think maybe it would be good if we can say what it is that we believe...
numeric evaluation of genfact
rk_adaptive: A more detailled warning message
rk_adpative test suite failure
rk_adpative test suite failure
integration error
Not a bug since applying ratsimp gives the original expression.
Use ratsimp(dy) and you'll recover your original expression. (%i6) ratsimp(dy); (%o6) x^3*sqrt(1-x^2)
integration error
Change name of function "contains" to "has_key" following discussion on mailing list circa january 2026.
Check that makeinfo version is > 5.1
Merge branch 'master' into rtoy-highlightjs-example-maxima-blocks-texi-dev
Use a dark blue for the dark mode example background
Update version check for makeinfo
Include pygments custom CSS when using pygments style
Add pygments.custom.css
Move pygments css from manual.css to another file
Use pgyments option -O classprefix=pyg-
Use pgyments option -O classprefix=pyg-
Use HERE docs for variables and fix a typo
Remove debugging statements
Forgot to AC_SUBST CUSTOM_PYGMENTS_CSS
Require at least 7.2dev for custom-pygments
Document custom-pygments for the syntax-highlighting option
Don't include the patch number if it's 0 for the version string
Put back SET_HIGHLIGHT
Remove pygments inline CSS from manual.css
Add some comments on what we're doing
If custom-pygments, load up separate CSS files for the styles
Support custom pygments
Get pygments default and rtt for the styling
Add support for custom-pygments for syntax highlighting
Print the version out again; add some comments
Add shell function to extract makeinfo version number
First cut at using new texinfo custom highlighter.
Support dark mode too for pygments
Make the background for pygments to match examples
Fix typo in error message about pygments
Use correct CSS comment style; change line-height
Fix bugs in testing value of syntax highlighting
Update CSS for pygments
Configure --enable-syntax-highlighting for highlightjs/pygments
wrstcse: Made the example for the new function actually use tolerances
wrstcse: A test for the new function.
wrstcse: Documentation of the new function
Package descriptive: function mean now returns und for empty input.
wrstcse: Add another plausibility test for wc_systematic.
wrstcse: Enable the monte-carlo-analysis for the numerical wc_mintypmax
wrstcse: A command that does a worst-case-analysis numerically.
#4554 trigrat often makes expressions unnecessarily complicated
Change from `defun` to `defmfun` user-level functions. No unexpected testsuite or share testsuite failures with SBCL 2.4.7.
#2596 error in matrix exponentiation
append fix for #4634 to ChangeLog
#4634 Divergent integral simplifies to -1/4 with simplify_sum
verbify("!!")
Fixed by commit [ 9439e6 ].
Associate "!!" with %GENFACT in *OPR-TABLE*.
rk_adaptive: Made it work with reverse limits, as well
rk_adaptive: Another sanity check
rk_adaptive: Speedup by compilation
rk_adaptive: Speedup by recycling calculation results
Windows installer: Update SBCL.
rk_adaptive improvements:
A runge-kutta method with adaptive step size.
wrong TeX output with unary plus in exponent
Could you build your own? In any case, I'm closing this report since it doesn't happen with recent versions of Maxima.
Tested with 5.44.0 and 5.45.1. The systems I use don’t have newer versions, sorry.
rk_adaptive: Automatic tests
Resolved another texinfo warning
Resolved a texinfo warning
Made the Textinfo doc work again
Same in the slightly older release Maxima 5.48.1 SBCL 2.5.7
What version? I don't see this issue with current git HEAD: (%i1) simp:false; (%o1) false (%i2) tex1(x^+y); (%o2) x^{+y}
wrong TeX output with unary plus in exponent
verbify("!!")