Waldek,
Thanks for the lisp command you have given to compile and load a Lisp file.
Good to know.
I have also augmented the dynamic memory space as you suggested and you're
right, that fixed things. I rebuilt FriCAS though, I don't know how to pass
argument to the underlying Lisp at startup via
Hi Martin,
I appreciate your monospace.spad, but it looks like it is not yet perfect.
(13) -> nthRoot((4+1/b)/sqrt(a+b),5)
+-+
| 4 b + 1
(13) |-
5| +-+
\|b\|b + a
5 +---+
\| +-+
4*b+1/b*\|b+a
Obviously, your /
I had a look into my notes and the case is
)read can read a Lisp file if it ends in *.lisp (*.lsp doesn't work)
This seems to be an undocumented feature? (nothing to do with my hack)
(3) -> )read TMFORM.lisp
; compiling file "C:/git-sdk-64/mingw64/lib/fricas/target/x86_64-w64-mingw32/src
> I find it useful to have up to date ChangeLog in file. I must
> admit that I do not undertand "burden" above: I write ChangeLog
> enty just before commiting to mainline (earlier I do not have
> enough info to write the entry). So it does not exist in
> code under development and only changes
On Sun, Mar 22, 2020 at 10:13:23AM +0100, Ralf Hemmecke wrote:
> Hello,
>
> up to now we have for each and every commit an entry into the ChangeLog
> file. If we follow the convention for git commit messages, see for
> example here...
>
> https://chris.beams.io/posts/git-commit/#seven-rules
>
>
You have to ")fin ... (|spad|)" of course (forget to mention).
Is not a good idea anyway, you're right; I have hacked the boot code to read
inline lisp code but that's certainly not to recommend.
On 29.03.2020 20:20, Grégory Vanuxem wrote:
> Kurt,
>
> TMFORM file is pure Lisp whereas the )read
On Sun, Mar 29, 2020 at 08:04:13PM +0200, Gr??gory Vanuxem wrote:
> Hello here,
>
> I'm trying to spot a bug in my MSYS2/MinGW configuration, the build process
> shocks on TMFORM (texmacs format) if I build FriCAS from scratch i.e.
> without pre-generated files. With pre-generated files all is
Kurt,
TMFORM file is pure Lisp whereas the )read command expects FriCAS
interpreter language.
So no success of course ;)
Greg
Le dim. 29 mars 2020 à 20:12, Kurt Pagani a écrit :
> Usually ")read" can also read a lisp file (provided it ends in *.input):
>
> $ cp TMFORM.lsp TMFORM.input
>
>
Usually ")read" can also read a lisp file (provided it ends in *.input):
$ cp TMFORM.lsp TMFORM.input
)read TMFORM
...
No guarantee, though ;)
On 29.03.2020 20:04, Grégory Vanuxem wrote:
> Hello here,
>
> I'm trying to spot a bug in my MSYS2/MinGW configuration, the build process
> shocks
Hello here,
I'm trying to spot a bug in my MSYS2/MinGW configuration, the build process
shocks on TMFORM (texmacs format) if I build FriCAS from scratch i.e.
without pre-generated files. With pre-generated files all is right.
So :
1) which Lisp compiler compile pre-generated .lsp files? It
On Mon, Mar 23, 2020 at 08:03:21PM -0700, 'Nasser M. Abbasi' via FriCAS -
computer algebra system wrote:
> Fyi, found another one with the same problem. I found this happens when
> setting setSimplifyDenomsFlag(true)
>
> If I do not issue setSimplifyDenomsFlag(true) before, then the
On Mon, Mar 23, 2020 at 01:03:06PM -0700, 'Nasser M. Abbasi' via FriCAS -
computer algebra system wrote:
> Could someone please explain why this call to integrate fails first time,
> but works second time?
>
> Running 1.3.6 on Linux Manjaro under Virtual box
>
> (1) ->
Ralf
Back in 2014 I wrote some SPAD code to output 2D text with the same sort
of interface as i-output but it could easily be adapted for other
interfaces:
https://github.com/martinbaker/multivector/blob/master/monospace.spad.pamphlet
It is documented here:
Hi everyone,
the following text is part of a private discussion following my offer of
TexFormat (and other formatters to come).
On 3/27/20 4:55 PM, Waldek Hebisch wrote:
> Well, I would like to avoid having a lot of output streams and
> similar but not identical formatters. If one really needs
14 matches
Mail list logo
