> Anyway, sorry to be such a bother, but how could I permanently
> change/disable the C-TAB binding the maxima modes use? I prefer to use
> it to switch between buffer windows.
Another problem with C-TAB, I suppose, is that it isn't always
recognized if emacs is run in a terminal.
I wanted the two types of completion (dynamic completion, where the
possible completions are cycled through in the buffer, and non-dynamic
completion, where possible completions are displayed in a different
buffer) to be bound to <something>-TAB. What I can do is just use
M-TAB, and make which type of completion is to be used a user option.
> A Quick and Dirty Introduction to EMaxima seems to have the keybindings
> wrong for quite a few of the maxima mode commands. Is this something
> that is overriding them at my end? They binding as shown in the maxima
> mode help seem to work OK though.
I'll fix after I change the keybindings (as mentioned above and below).
(I don't know why, but the introduction is in three places:
doc/emaxima
doc/maximabook/interfaces
interfaces/tex/EMaxima
I'll change it in all three places.)
> While I'm complaining... M-backspace also seems to be rebound. Perhaps
> this should also be rebound to something else, since I think most people
> expect M-backspace to kill the word to the left of the cursor?
...
> Well, I commented something out of maxima.el, so I guess that wont work
> now. I'll see if I can find the line I commented out...
>
> (define-key map "\M-\C-h" 'maxima-mark-form)
>
> This confused me slightly, since C-h does not mean backspace in emacs,
> as far as I am aware... The help however says
C-h is backspace in a lot of terminals, and sometimes in emacs, I
suppose (not here, though). Since M-h is bound to mark-paragraph,
which doesn't seem to be too useful for Maxima, I can rebind
maxima-mark-form to M-h.
> OK, when I am in a maxima interactive session and I do
> C-c C-d
> Maxima Help: array
>
> I get: Wrong type argument: sequencep, #<keymap size 0 0x5539>
I fixed this, and put the fix in cvs.
I'll put the font-lock changes and the key-rebinding changes in soon
unless there are any objections.
> Oh, another thing, the maxima process seems to keep getting killed for
> no reason. Running xmaxima I have never so far had any crashes/dead
> processes. Any idea what is going on?
No, this is bad. I haven't come across this yet.
Jay