569 Reputation

13 Badges

12 years, 316 days

MaplePrimes Activity

These are replies submitted by itsme


I wonder why the choice to use method(arg,object), and not method(object, arg), was made.

The latter seems much more natural to me, as the position of the 'object' is always the same, and does not depend on the signature of the method.



right... for me, these days, i find it harder and harder to use the worksheet interface (no useful key bindings, no syntax highlighting), and use an outside editor even for smaller calculations if analytics are required. The pain of *constantly* reaching for a mouse, every few seconds, on every edit, is unbearable (i'm only exaggerating slightly ;) ) after many years of vim (or emacs i'd imagine). This is even more true with Mathematica due to its inherently functional programming style, which often involves writing code "outward" (i.e. new statements wrap older ones).

For those who may be interested, there is a beautiful plugin for jupyter-notebooks (jupyter-vim-binding) that allow one to use (basic) vim modes for editing - works with whatever kernels are supported... for me it's a game changer, and the editing experience in jupyter is magical... no mouse needed essentially.
Now if only maplesoft provided a kernel for juputer-servers... that would be something!


@Joe Riel thank you for sharing!...

would would the advantage be of doing things this way, vs just calling "raed package.mpl"? i guess i don't know what one gains by writing a "package", other than things get imported/loaded differently.

also.. so say you've made changes in your package, you hit a hotkey in emacs/vim, things get "complied" and the package gets updated in your packages directory that maple knows about. I assume you then have to manually reload it in maple? or is there a way to make this happen automatically?

thanks again.


i also use vim for writing code, but then just make:

read "code1.mpl"

read "code2.mpl"

type statements in my worksheet.

if you have something you're willing to share (don't waste time with anything new - this is no big deal), could you give an example of a more complicated module you've written this way, and how it's being used/imported/read?

Also, is there a way to have maple automatically update/reread a file/module on change? so say i've reaad/imported one, then update it in a separate editor, and would like a running maple session to automatically reload it.




you could try installing the physics package from within maple via:


(maybe worth while removing whatever you've installed before though)


thanks for the workarounds.

I was hoping Eigenvectors() would support "implicit=false", in the same way Eigenvalues() seems to. I guess this is a bug/limitation then.




very helpful, thanks for posting.


@Kitonum  @vv

thanks for you suggestions. They do work indeed.

Was hoping there is flag to maple's simplify that i missed and that would help it do this... i have some number of similar expressions (within larger expresisons), and so this wil help.

I'm kind of impressed that mathematica does, what i would consider, the right thing in these cases.


the "spurious" sequence \[] is how you define special/greek characters in mathematica using standard ascii (this is what i meant by referring to lprint). Maple has some understanding of them. Try:

a1:=convert("\[Kappa] + \[Lambda]  + \[Gamma]", FromMma);

lprint(a1); #looks like the right thing.

It seems to get confused, however, once some implicit multiplication is involved (perhaps along with these "special" characters).

This seems like a bug to me. 



the "spurious characters" are mathematica's lprint version of the greek letters in this case - note that they are actually correctly interpreted. This is just doing a standard copy/paste (i'm using Mma 12.0 at the moment). It seems that the parenthesis seem to confuse the translator.

Just wanted to double check if i'm not missing something obvious; but maybe not... i guess will submit a fault report.

EDIT: hmm.. maybe because the multiplication is not explicit, maple doesn't know if it should interpreted the parenthesis in the context of a function with its depenednt variables, or just grouping of terms... but in this case, it does seem obvious.


no worries.

i was guessing that's actually what you were doing. I meant that you could still write your 'data' string to a temp file from within maple after you extracted it from a database - then "read()" that file. It's not pretty, but all the parsing is done automaticlly in that case (with hopefully no gotchas).


thanks. of course you're both correct!

...long day.

ok it looks like


seems to work with a few simple examples i tried. I was going to delte this question, but i guess i will leave it in case it's useful for someone else.


@vv  @Rouben Rostamian

While we're at it... exporting plots via cmaple interface is also does not work. (cmple interface can be very useful if one, say, wants to run code in batch mode, produce plots and save them - for example on a cluster, remote headless machine, etc).

Regarding exporting to pdfs and bounding boxes. Some time ago, I had some luck manually editing the pdf post export to fix some issues with the bounding boxes. This can also be done programatically via a script, etc. But surely it's a last resort "solution"...

I agree, it would be nice to get export working reliably, and maybe more sophisticated plotting abilities (eg: color bar for contour-filled, density plots, etc)

Hi @Stephen Forrest 

my take on this would be that by default, a call to latex() should:

1) always use \frac{a}{b} only

2) add no extra (latex) white space characters.

I agree with @Leo Brewin  a/b can be useful in inline equations, however, this if often done for shorter expressions and those are easy to type anyway. The real power of a usable latex() command would be for the long expressions/matrices/etc that are really painful to type out.

Regarding (2), I do sometimes use white space characters, but this is often done when defining commands or special characters, and very rarely to "manually typeset" equations.

Having some of these things user-settable via an argument passed to latex could also be an option, as you suggest.

1 2 3 4 5 6 7 Last Page 1 of 15