diff --git a/configure.ac b/configure.ac
index 073f3e96..0c66c8de 100644
--- a/configure.ac
+++ b/configure.ac
@@ -452,6 +452,8 @@ case $fricas_lisp_flavor in
sbcl)
fricas_quiet_flags='--noinform --noprint --no-sysinit
--no-userinit'
fricas_eval_flags='--eval'
+
OK, in attachment are 2 patch files, please review.
First one fixes several problems:
1. The most outstanding bug is that the width and height should
exchange positions in BoundingBox!!
2. The logic to determine scale factor is a mess, including
several minor logical problems.
And I extract it
On Sun, Apr 07, 2024 at 06:05:39AM +0200, Grégory Vanuxem wrote:
>
> It is possible to modify some parameters to Float output routines,
> what about returning the previous settings? For example
> outputSpacing(n) returns Void but if you want to temporarily modify
> this setting, in Spad for
One of the reasons that started me looking at a non-Lisp base was the
fundamental use of lists in the Boot implementation. Within Icon (or in my
case using the Unicon system), lists are implemented in such a way that
accessing any element was much faster than via a cons cell. You could treat
a
On Fri, Apr 12, 2024 at 06:25:26PM +0800, Qian Yun wrote:
> We have discussed this before, namely the default dynamic-space-size
> is not enough during build.
>
> Recently there is a github issue hitting by this on freebsd.
>
> I get hit by this issue a few times as well, because the default
>
On Sat, Apr 13, 2024 at 05:25:17PM +0800, Qian Yun wrote:
> One of the problems of postscript files generated by "draw" is that
> it is not proper "embedded postscript file", aka "eps".
>
> When trying to include such image files in latex document, there are
> huge padding around image.
>
> The
On 13 April 2024 02:38:34 CEST, Hill Strong wrote:
>There is nothing to stop anyone from breaking the requirement of using any
>Lisp as the destination for Boot code. I translated one section of Boot
>code directly into Icon. Of course there is much in Boot than assumes Lisp
>lists. But that
One of the problems of postscript files generated by "draw" is that
it is not proper "embedded postscript file", aka "eps".
When trying to include such image files in latex document, there are
huge padding around image.
The problem is caused by "BoundingBox". We have "BoundingBox" in
generated
Hello,
So what about writing a dedicated )hd routine or whatever name is
chosen so that HyperDoc receives signals from FriCAS ? As Waldek has
said, most programs will not read standard input.
Le sam. 13 avr. 2024 à 05:53, Qian Yun a écrit :
>
> The normal "hypertex" (started by sman) receives
Hello Waldek,
,
> > And to coerce the Float to OutputForm convert(Float)@String is used.
> > But with default settings the bits(n)$Float routine is used to change
> > the precision in bits before performing the transformation to a string
> > and it uses the mantissa which is for 8.5 (17 . -1) only
10 matches
Mail list logo
