Hello Bill

On Saturday, 13 September 2014 06:24:21 UTC+2, Bill Page wrote:
>
> Kurt, 
>
> Thanks for the example output. I am glad that it works and maybe it is 
> still an argument to include gnuDraw in the next release even if we do 
> not extend the TeXmacs interface to use it easily. 
>

*By all means*. I wonder anyway why it's not yet included. 

 

>
> I have never tried it but I thought maybe you could use the TeXmacs 
> gnuplot plugin? 
>
> http://www.texmacs.org/tmdoc/plugins/gnuplot/gnuplot-main.en.html 
>
>
A valuable hint, thank you. It's using a shell script "tm_gnuplot" which 
utilizes the 'ps' command of TeXmacs, otherwise it works along the same 
lines, i,e. generating a temp postscript file.   

 

> Your serializer plugin looks interesting.  Are you suggesting that a 
> much enhanced version of 
>
>   tmm(s:String):String == s 
>
> might be used as a kind of TeXmacs mathmode interpreter for FriCAS? 
> I.e. It sees "int(a,b,f(x)dx)" from TeXmacs, executes 
>
>   integrate(f(x),x=a..b) 
>
> then sends the result back to TeXmacs to be rendered? 
>
>
Indeed. However, the problems are numerous: simple expressions work well by 
some string manipulations, yet one has to consider that the user might not 
like how 'dx' is represented, for example, so he could insert whitespace 
which arrives as 'd x'. Similar problems arise if one forgets the '*' in 
multiplication operations etc. (see the example pdf).
I suppose that one needs a grammar+parser in order to get more than a toy. 
Even nested integrals may be hard to deal without some minimal (context 
aware) rules. One positive feature of the plugin init files is that one can 
easily map the keywords, e.g.

("<in>"           " @in ")
("<cap>"          " @cap ")
("<cup>"          " @cup ")
("<subset>"       " @subset ")       

so that they are properly separated (e.g. otherwise "\forall x \in S" => 
"forallxinS" ;)
I really don't know what's the best solution, maybe a combination of a 
packrat grammar (as described in 5.3)  on the TM side and a transformer on 
Fricas side?

BTW is 
tm_eval(s:String):Any ==
   inpForm:=parse(s)$InputForm
   interpret(inpForm) 

the correct way to evaluate string commands? The completer gives a 
'interpretString', but I didn't find any information to that.

Kurt
  




 

>
>

-- 
You received this message because you are subscribed to the Google Groups 
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.

Attachment: exdefint.pdf
Description: Adobe PDF document

Reply via email to