Activity for Maxima -- GPL CAS based on DOE-MACSYMA
-
Raymond Toy posted a comment on ticket #4692
Are you going ;to leave gcl broken then? FWIW, I have offered to help Camm with unicode, but he wants strings to be utf-8 and I don't see how that can possibly work when you can do arbitrary writes to anywhere in the string. Maybe I lack imagination.
-
Add more documentation, especially regexes
-
Allow pprinting of the results
-
Don't need compat.lisp; remove it
-
Add support for other lisps. Get rid of call to set-stdout-utf-8.
-
Robert Dodier posted a comment on ticket #4692
@jgmbenoit Can you consider working with a different Lisp implementation? I recommend SBCL. From a technical point of view I think it is preferable.
-
@villate Jaime, thanks for posting the example output. I see that it is ASCII-only; the quote marks are ASCII single quote and the item markers are ASCII asterisks. I suggested in another comment that one way to get this to work with GCL may be to enable the --no-utf-8 flag for makeinfo.
-
@rtoy Thanks for working on it, but I dunno, reworking read-info-text looks like a bridge too far for me. If there is some desire to make Unicode stuff work for GCL, maybe you can invest the same time and energy in GCL. Or maybe not, as you wish, either way is A-OK by me. @rtoy @jgmbenoit @villate The Interwebs claim that makeinfo has a command line flag --no-utf-8. If someone wants to package Maxima with GCL, that flag could be enabled. The examples in the Texinfo documentation are already using...
-
Whether or not the index generator is Lisp or Perl is beside the point for the purpose of resolving the bug report -- the problem is that GCL doesn't understand multi-byte characters. @l_butler, with all due respect, can you please open a separate ticket to pursue the reimplementation of build_index.pl, should you choose to take up that topic.
-
Hello, I can also build Maxima with GCL 2_7_2pre6 and It has no problem with UTF8. The following is a session in Xmaxima: Maxima branch_5_49_base_190_gdc4d613d6_dirty https://maxima.sourceforge.io using Lisp GNU Common Lisp (GCL) GCL 2.7.1 git tag Version_2_7_2pre6 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) ? build_info -- Function: build_info () Returns a summary...
-
The last time I tried it didn't actively support unicode. Bit since it seems to treat text just as a stream of octets it didn't hinder you from using unicode. As long as you don't need to know how many characters the octets wou use count as in unicode and as long as you don't cut a unicode multi-byte sequence into two halves you won't notice any difference.
-
Lisp version of build_index.pl
-
I pushed commit [ 4be0ef ] to fix the problems with plotting options -- just replacing $BOX with MBOX throughout. I don't think the things that are described in this ticket are bugs. There is no guarantee that foo in user input corresponds to $FOO in Lisp.
-
Leo Butler committed [ed397c] on Code
doc/info/README: remove TODO item PDF Hyperlinks
-
Jaime E. Villate committed [5e9c76] on Code
Changed the first plot2d example in the Introduction.
-
Updates the plot3d example in the Introduction chapter of the manual.
-
Adds a comment with the Maxima version and date/time in the graphic files.
-
Robert Dodier committed [4be0ef] on Code
Replace all instances of $BOX relating to plot options with MBOX,
-
Merge branch 'rtoy-specvar-var-par-in-hypgeo'
-
Add comment about what vfvp stands for
-
Remove *hyp-par* and freepar and friends
-
Remove use of *par* in $hgfpoly
-
Remove uses of *par* in hgfred, 2f1polys, legfun
-
Actually use the new condition type and more cleanups
-
Clean up implementation
-
Change the last clause in cod from otherwise to T.
-
Fixes a missing parenthesis in plot.lisp
-
I think many years ago Rupert Swarbrik (?) started on a lisp replacement for build_index.pl. Never finished. I'm not sure how that would work if a Lisp doesn't have unicode support, but it would probably be easier today since we have pregexp support. I have thought about using m4 to do update_examples, so that everytime the manual is generated, the examples are too. But not sure if that's a good idea because it would probably really slow down generation of the docs. Plus, someone would have to check...
-
build_index.pl (and update_examples) are anachronisms. Irregardless of how we fix this bug report, I think the best way forward would be to re-write this perl script in lisp and generate the index file at run-time, not build-time. BTW, it is an embarrassment that we use perl and not lisp to do this simple text stuff. There may have been a time when that made sense, but that is long gone.
-
Fix #4692: Add utf-8 decoder for gcl to read info files
-
Here is a replacement for read-info-text in cl-info.lisp that appears to work for me with gcl. "? build_info" isn't truncated. (defun read-info-text (dir-name parameters) (let* ((value (cdr parameters)) (filename (car value)) (byte-offset (cadr value)) (char-count (caddr value)) (octet-buffer (make-array char-count :fill-pointer 0 :element-type '(unsigned-byte 8))) (path+filename (merge-pathnames (make-pathname :name filename) dir-name))) (handler-case (with-open-file (in path+filename :direction...
-
Did some poking around in cl-info::read-info-text. For "? build_info", the starting point of 52615 in maxima.info-1 is correct. However, the expected length is 3596. If you read 3596 octets starting from 52615, you get a truncated result, ending exactly with "the variables ‘maxima_fro". But if you read 3596 characters, you get the correct end point. The issue is the there are backquote characters, specifically Left_Single_Quotation_Mark, #u2018. That's encoded as 3 octets: 226, 128, 152. What's the...
-
New definition of palette for plot3d.
-
Still truncated. Not sure why. It will take some time to debug.
-
Yeah, I see that it's truncated now. The build was on some random branch. I'm redoing it now, and making sure I run make in doc/info. It will take a little while to rebuild all of maxima with gcl. I'm also using the texinfo 7.3 (self-built from the 7.3 release tag).
-
Jerome Benoit modified a comment on ticket #4692
So it appears that your (Raymond Toy) description is also truncated.
-
I play with the latest unstable packages of gcl27 and maxima. The current texinfo version in unstable is 7.3-2.
-
Hello, I can also build Maxima with GCL 2_7_2pre6 and It has no problem with UTF8. The following is a session in Xmaxima: Maxima branch_5_49_base_190_gdc4d613d6_dirty https://maxima.sourceforge.io using Lisp GNU Common Lisp (GCL) GCL 2.7.1 git tag Version_2_7_2pre6 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) ? build_info -- Function: build_info () Returns a summary...
-
So it appears that your description is also truncated.
-
Jerome: What version of texinfo are you using? In Ubuntu, with texinfo 6.8-4build1 and GCL git Version_2_7_2pre6 I don't see any problem: Maxima 5.49.0 https://maxima.sourceforge.io using Lisp GNU Common Lisp (GCL) GCL 2.7.1 git tag Version_2_7_2pre6 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) ? build_info -- Function: build_info () Returns a summary of the parameters...
-
$ echo "? build_info" | ./maxima-local -g -l gcl Loading /home/toy/.maxima/maxima-init.lisp Loading /home/toy/.maxima/maxima-init.mac Maxima branch_5_49_base_256_g15f37747e https://maxima.sourceforge.io using Lisp GNU Common Lisp (GCL) GCL 2.7.1 git tag Version_2_7_2pre12 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) -- Function: build_info () Returns a summary of the...
-
Can you give the output of echo '? build_info' | maxima ?
-
For the record I just built gcl Version_2_7_2pre12. I compiled maxima with it (from scratch). ? build_info has the expected result. No extraneous text or missing text. My build only set --prefix. I didn't use any other options for configure.
-
Gunter Königsmann posted a comment on ticket #4692
The last time I tried it didn't actively support unicode. Bit since it seems to treat text just as a stream of octets it didn't hinder you from using unicode. As long as you don't need to know how many characters the octets wou use count as in unicode and as long as you don't cut a unicode multi-byte sequence into two halves you won't notice any difference. On 5 April 2026 16:26:03 CEST, Raymond Toy rtoy@users.sourceforge.net wrote: Maxima startup says I'm using GCL 2.7.1 git tag Version_2_7_0. I...
-
Maxima startup says I'm using GCL 2.7.1 git tag Version_2_7_0. I built this myself from a git repo using the Version_2_7_1 tag. I have not yet updated to a newer version. The version that comes with my OS is GCL 2.6.14 git tag Version_2_6_15pre17. I don't think I've tried building Maxima with this version, but I think I used to use 2_6_14 previously, which is, I think, the oldest version that Maxima supports. I'm almost 100% sure that Gcl does not support unicode. Pretty sure Camm would like to have...
-
Fix a typo and clean up a few comment indentations
-
I could not reproduce the claim of Raymond by building from the vanilla source balls of gcl27 and maxima. Furthermore I have seen no evidence that GCL has move to UTF-8. I am also looking for a quick fix.
-
Here is the out put of the shell command echo '? build_info' | maxima: Maxima 5.49.0 https://maxima.sourceforge.io using Lisp GNU Common Lisp (GCL) GCL 2.7.1 git tag Version_2_7_2pre13 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) -- Function: build_info () Returns a summary of the parameters of the Maxima build, as a Maxima structure (defined by âdefstructâ). The...
-
Why don't you first check with Raymond what GCL version he is using. Apparently it's a different version from the one you use in Debian sid, because he doesn't see that problem.
-
I could fix the issue in Sid by reversing commit 20cfb9d8084 ("In build_index.pl, assume info file encoding is always UTF-8."). I guess that this move is currently too drastic. It might be still permitted to pass the char-encoding as argument with UTF-8 as default.
-
Remove *par*
-
Merge branch 'master' into rtoy-specvar-var-par-in-hypgeo
-
Add comment about what vfvp stands for
-
Remove *hyp-par* and freepar and friends
-
Remove use of *par* in $hgfpoly
-
Remove uses of *par* in hgfred, 2f1polys, legfun
-
Revert "In f35p147test and f35p147 pass in the Laplace parameter"
-
Revert "Pass in the Laplace parameter in more places"
-
Revert "Pass in the Laplace parameter in lt-exp"
-
Pass in the Laplace parameter in lt-exp
-
Pass in the Laplace parameter in more places
-
In f35p147test and f35p147 pass in the Laplace parameter
-
Rename *var*/*par* to *hypgeo-var*/*hypgeo-par*
-
alt-display breaks trace's output
-
With the patch: maxima-local Maxima branch_5_49_base_188_g2bd018694 https://maxima.sourceforge.io using Lisp SBCL 2.6.0.debian 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) load("alt-display.mac"); (%o1) /home/x201-work/work/maxima/sandbox/git/maxima-code/share/contrib/alt-di\splay/alt-display.mac (%i2) ff(n) := if n=1 then 1 else n*ff(n-1) $ (%i3) trace(ff) $ (%i4) alt_display_text_prefix:"<mtext>"...
-
This is fixed in commit a0348f57.
-
alt-display.mac: Fix bug #4698 alt-display breaks trace's output
-
Wolfgang Dautermann committed [242d9d] on Code
Windows installer: Update SBCL.
-
Changed the name of the new option light to lighting.
-
Add comment about what vfvp stands for
-
More ipmprovements to Geomview plot3d plots.
-
The attached patch also works, too.
-
alt-display breaks trace's output
-
Fixed a typo.
-
More plot3d options.
-
Several improvements to plot3d.
-
Oh, that is annoying. :lisp $%i1 shows that it's been converted to ((MSETQ) MBOX 5). That seems wrong.
-
Yes, that's the gilty commit. More on this bug: (%i1) box: 5$ (%i2) box; (%o2) 5 (%i3) :lisp $box Maxima encountered a Lisp error: The variable $BOX is unbound. Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. (%i3) :lisp mbox 5
-
I do not know, but a quick grep through git log suggests that commit [13a361] introduced this change. It fixes a bug reported on the list about boxed objects being noun/verb confused.
-
Symbol $box being changed to mbox
-
Remove *hyp-par* and freepar and friends
-
Remove use of *par* in $hgfpoly
-
Remove uses of *par* in hgfred, 2f1polys, legfun
-
Fixes function hsv to accept expressions that simplify ot numbers between 0 and 1.
-
tex and lurkmathml typeset itensor output incorrectly
-
dan hayes posted a comment on ticket #4691
that issue u last commented has been solved meaning it does now bring up the new version . the only issue now is just my above comment the bug in that the startup commands box is frozer one cannot access it in maxima -you cannot type anything in that box 'Start up commands' you cannot edit the box 'Maxima commands to be executed every time wxMaxima starts Maxima'. you cannot type anything in there to change what is already there . Also the same goes for the box you fill out if desired for 'Maxima...
-
Fixed an error in the dlcumentation for Plotting.
-
Attached is a comparison of pre- and post-patch tex output.
-
tex output for an input label %i1 is inconsistent
-
lurkmathml does not know how to typeset box
-
Fixed in commit b78b96e89.
-
lurkmathml does not typeset x_1 correctly
-
Fixed in commit 69981c5f6.
-
lurkmathml does not typeset z[2]^3 correctly
-
Fixed in commit 14e87d819
-
mathml.lisp: fix non-validating mathml in MATHML-INT
-
share/contrib/lurkmathml/doc/Makefile.am: add html target
-
lurkmathml: Fix bug #4694 typeset box
-
share/contrib/lurkmathml/doc/mathml.texi: improve documentation
-
share/contrib/lurkmathml/example.mac: additional subscripting tests
1 >
