============================================================================== Known bugs ============================================================================== The installation procedure, and in particular the rpm, does not always find properly the emacs site-start.d directory to put mupacs.el inside. The problem is that this changes from distribution to distribution. Redhat/Fedora: /usr/share/emacs/site-lisp/site-start.d Mandrake: /etc/emacs/site-start.d ? Some other distributions do not have a site-start.d directory anyway, so we need to modify directly the site-start.el file ... The mupacs-3.2.2 rpm completely missed the mupacs.el file ... ------------------------------------------------------------------------------ Fontification of medium to large MuPAD files is slooooowwww ... ------------------------------------------------------------------------------ vcam does not redraw a 3d scene after a rotation The same thing occurs with the text-mode MuPAD ------------------------------------------------------------------------------ To follow the usual convention, mupad-mode should toggle on and off the mupad-mode, unless an argument t is given. ------------------------------------------------------------------------------ (2004/04/19) MuPAD 3.0.0 never yields back the hand after: system("ls -l troc"); ------------------------------------------------------------------------------ The example in ?system does not work: since MuPAD is called with the -R option, system calls are delegated to the interface and are not synchronized (that's a MuPAD bug which also appears in xmupad). Work around: use 'shell::system' from the `shell' dynamic module. ------------------------------------------------------------------------------ system should only block the *MuPAD* buffer not all of emacs; in fact the *MuPAD* buffer should behave as when it is waiting for a MuPAD computation. ------------------------------------------------------------------------------ customizing mupad-directory does not reset mupad-help-file-name-tar accordingly ============================================================================== Bugs with unknown status ============================================================================== Sending this multiline input to the debugger hangs it. proc() begin 1 end Could not reproduce (3.2.2 2004/12/01) ------------------------------------------------------------------------------ res TAB says no completion available ? could not reproduce (3.2.2 2004/12/01) ------------------------------------------------------------------------------ There are cases where the name of the program is ignored? ------------------------------------------------------------------------------ (probably fixed by a bugfix with sexps) Dans un fichier bla.mu contenant les lignes suivantes; partir du ";" à la fin du map, effacer tout avec backspace jusqu'au "m: dom" compris, puis essayer de revenir en arrière avec undo. Chez-moi il affiche "No further undo information" avant d'avoir remis tout le "map ..." en place. ------------------------------------------------------------------------------ (fixed? 3.2.3 2004/12/01) Make sure that the in-buffer completion list is always completely visible; There are cases where there seems to be a conflict with the recentering heuristic, and all the completion lists is below the last visible line ... ------------------------------------------------------------------------------ ?_power Where is the problem? (3.2.3 2004/12/01) ------------------------------------------------------------------------------ mupad300; debug(combinat::compositions(4)) ; s s s s s s mêne à un MuPAD dans les chous Est-ce du au modifications récentes pour la gestion de /tmp/debug* Works for me (mupad-3.1.0 2.2.3 2004/12/01) ============================================================================== Fixed bugs ============================================================================== (fixed 3.2.3-4 2005/01/21) Missing dependency of mupad-run on mupad (for mupad-start-manual) ------------------------------------------------------------------------------ (fixed 3.2.3 2004/12/15) With the -E protocol and MuPAD < 3.1.1, mupad-run does not display the file/line the debugger is running on. ------------------------------------------------------------------------------ (fixed 3.2.3 2004/12/01) mupad-run-commandline could not be customized to an arbitrary user string ------------------------------------------------------------------------------ (fixed 3.2.3 2004/12/01) Those options should be set by default when the user has no mupad-run-mode-hook: (custom-add-option 'mupad-run-mode-hook 'mupad-help-init) ------------------------------------------------------------------------------ (fixed: 2003/01/29) mapc is missing in emacs < 20.7 There remains some error about wd. To be investigated. ------------------------------------------------------------------------------ (fixed: 3.2.2 2003/10/27) Fixed caar in sli-maid-get-alist. The following error message was printed on loading mupacs: Something went wrong in sli-tools: (wrong-type-argument listp %if) and afterward closing end_if with C-c C-e did not work. ------------------------------------------------------------------------------ (fixed: 3.2.2 2003/10/27) sli-show-sexp caused spurious debugging output. ------------------------------------------------------------------------------ (fixed: 3.2.1 2003/09/28) mupad-run was broken when mupad-run-recenter-behaviour is set to nil. On starting of mupad-run, and after each input line, the following error message was issued: error in process-filter: cond: Wrong number of arguments: #, 1 ------------------------------------------------------------------------------ (fixed: 3.2.1 2003/09/28) @lisp_dir@ is not substituted correctly in mupacs.el: (setq mupad-el-info "${datadir}/emacs/site-lisp/mupad.el-info") ------------------------------------------------------------------------------ (fixed: 2003/05) mupad-run-mode got confused if undo was called enough times to revert the insertion of the last mupad output (the markers mupad-run-todo and such probably became incoherent). Fix: the undo list is now flushed after each command is inserted in the todo list, and after each insertion of a prompt. See the comments in the code. Any other places where we should do that? (fixed 3.2.4 2005/03/11) Yes, after a debugger prompt! Fix: factorize all the prompts display code at a single place ------------------------------------------------------------------------------ (fixed) Hitting backspace right after the xx in the line below in MuPAD mode seems to run into some infinite loop: proc(xx) Same thing when erasing with backspace starting right before the i [ [ m[k][i] ] ] ------------------------------------------------------------------------------ (fixed: 3.2.3 2004/07/07) P and D are non-functionnal under the debugger P was not implemented in the kernel < 3.1.0! ------------------------------------------------------------------------------ (fixed: 3.2.3 15/12/2003) Le commentaire a l'air de poser problème dans mupad-run Max := proc(a, b) /* comment: maximum of a and b */ begin if a