On 01/04/14 23:58, Ralf Hemmecke wrote:
There is a variable $saturn. And the word saturn appears quite a lot
in fricas. Does anyone know its meaning and perhaps some history of it?
Ralf
In bookvol5.pamphlet it says:
The [[*features*]] variable from common lisp is tested for the presence
of
On 02/04/14 02:37, Bill Page wrote:
On 1 April 2014 21:17, Waldek Hebisch hebi...@math.uni.wroc.pl wrote:
...
In FriCAS you are not supposed to mix documentation and code.
If your documentation is usable from HyperDoc then it should
go into src/doc/ht or src/doc/htex. Otherwise doc is a good
TechExplorer Saturn
Aha!
Looking at
mathprint x ==
x := outputTran x
$saturn = texFormat1 x
maprin x
a connection with TechExplorer was already my suspicion, but I didn't
know that it was named Saturn.
What makes Saturn output in any way special in contrast to all the other
On 02/04/14 07:54, Martin Baker wrote:
On 02/04/14 02:37, Bill Page wrote:
I agree with you about going back to the original spad files but not
about going to hypertext. As far as I can see hypertext is an old
fashioned interface, in a small window on the screen, which I never use
because it
Ralf Hemmecke wrote:
What makes Saturn output in any way special in contrast to all the other
formatters?
AFAIK Saturn was intended to be _interactive_ rich interface.
This means some extra annotations in the output which are
not needed without interaction.
Is there any reason to keep all
On 2 April 2014 09:15, Waldek Hebisch hebi...@math.uni.wroc.pl wrote:
...
Concerning keeping it: Saturn code caused little trouble, so
to the moment keeping it less effort than removing it. Also,
it could be good starting point for rich interface. Texmacs
folks prefered Scheme for
On 2 April 2014 09:15, Waldek Hebisch hebi...@math.uni.wroc.pl wrote:
... Texmacs
folks prefered Scheme for cominitaction, but according to what
Andrey Grozin wrote we could also use tex/latex. Given that
retargeting Saturn code to talk to Texmacs makes sense and
probably would require less
Martin Baker wrote:
I agree with you about going back to the original spad files but not
about going to hypertext. As far as I can see hypertext is an old
fashioned interface, in a small window on the screen, which I never use
because it crashes too often. Its also very hard to contribute
On 04/02/2014 06:45 PM, Waldek Hebisch wrote:
In Internet era you never can be sure where the information is. Of
course, there are reliable and rich sources. But a lot is spread out
in various obscure places.
That's certainly true. Nevertheless it makes sense to encourage people
to transform
On 02/04/14 17:45, Waldek Hebisch wrote:
Martin Baker wrote:
If you can crash HyperDoc, please report. ATM I know one way
of crashing HyperDoc, namely if you give complicated parameters
to a type and request info about implementations (I am working on
a fix for this). If you have any other way
Bill Page wrote:
On 2 April 2014 13:24, Martin Baker ax87...@martinb.com wrote:
On 02/04/14 17:45, Waldek Hebisch wrote:
...
I expect others may see different results, perhaps it will work on other
peoples computer.
I get this by going to:
topics - graphics - new framework -
I guess that is the recent change that you mentioned?
git log -1 $(git blame configure.ac|grep MAYBE|awk '{print $1}'|head -1)
commit 79efcc76f6b57f3fabe7366f1e86526d7a5dea72
Author: Ralf Hemmecke r...@hemmecke.org
Date: Tue Jul 9 20:52:43 2013 +
re-establish HyperDoc content from
On 2014-04-02 7:08 PM, Ralf Hemmecke r...@hemmecke.org wrote:
...
that the over all design of HyperDoc kind of sucks.
Well, yes, but unless we have something better...
Just complaining doesn't help. Everyone is invited to improve
or replace HyperDoc by something more modern.
I was not so
13 matches
Mail list logo
