Current version of SAGE: 7.5.1 though this happened with several versions,
all binary install
Operating System: OSX 10.11.6
Version of Tex: Version 3.14159265-2.6-1.40.17 (TeX Live 2016); All
packages up to date
As previously mentioned, this was all what matches on the cloud for SAGE
and Tex.
On Thursday, June 1, 2017 at 8:34:55 PM UTC+1, Julie Beier wrote:
>
> So I guess this was the point of my message. What you just posted does
> *not* work for me. It says True for dot2tex installed, but I get the two
> different tex files (doing this on my computer versus on the cloud) and on
So I guess this was the point of my message. What you just posted does
*not* work for me. It says True for dot2tex installed, but I get the two
different tex files (doing this on my computer versus on the cloud) and on
my computer it does not generate something that works.
On Thursday, June
On Thursday, June 1, 2017 at 7:57:22 PM UTC+1, Julie Beier wrote:
>
> Dima,
>
> Sorry but I'm not sure I understand. I followed the directions in the
> sage help that say to do sage -i 'dot2tex'. That is done. But it still
> creates the different tex files, and I still have the problem.
>
Dima,
Sorry but I'm not sure I understand. I followed the directions in the sage
help that say to do sage -i 'dot2tex'. That is done. But it still creates
the different tex files, and I still have the problem. Nicolas's work
around makes the small example he posted work, but it doesn't work
On Thursday, June 1, 2017 at 7:23:29 PM UTC+1, Julie Beier wrote:
>
> All,
>
> Thanks all for the help; glad to know it wasn't just something trivial
> that I missed.
>
> This work around doesn't seem to work for whole crystals as there is no
> set_latex_options option. Anyway to work around t
All,
Thanks all for the help; glad to know it wasn't just something trivial that
I missed.
This work around doesn't seem to work for whole crystals as there is no
set_latex_options option. Anyway to work around the problem there?
Best,
Julie
On Thursday, June 1, 2017 at 2:01:14 PM UTC-4, Ni
On Thu, Jun 01, 2017 at 12:02:19AM -0700, Dima Pasechnik wrote:
>How does one switch to using dot2tex for this example, too?
sage: t = StandardTableaux(4).random_element()
sage: G = DiGraph([[t,t]], loops=True)
sage: G.set_latex_options(format="dot2tex") # <==
sag
I would rather (replace my* with right values)
git checkout -b myrebasedstuff develop
git pull trac u/myuid/mygreatbranch
# assume it all merged fine, then
make doc-clean
make
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe fro
With master or develop, one should be all set. Just rebuild (./configure &&
make)
Sometimes
make doc-clean
would be needed,
in rare cases,
make distclean
is the only way forward.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscr
How does one upgrade with git? Is it enough to pull the master or develop
branch?
On Saturday, May 13, 2017 at 10:11:33 AM UTC-5, Dima Pasechnik wrote:
>
> IIRC, --upgrade is broken for years already, and should be removed.
> If you need to upgrade a source installation, use git; the correspondin
I have a ticket where I made some changes to the graph theory package. The
documentation wasn't compiling correctly, so I made and remade sage from
the develop branch and eventually got it working there. When I switch back
to my ticket and try to build the documentation, it says there's an error
Right, it is in fact invoking show(), which is
File:
/projects/sage/sage-7.5/local/lib/python2.7/site-packages/smc_sagews/sage_salvus.py
Source:
def show(*objs, **kwds):
"""
Show a 2d or 3d graphics object (or objects), animation, or
matplotlib figure, or show an
expression type
On Thu, Jun 1, 2017 at 2:59 PM, Dima Pasechnik wrote:
> right, sorry, I mean a sagews notebook running Sage.
> I did not try other SMC Sage interfaces.
Yes, there is probably somewhere this "show" function involved, which
has the same name but a different implementation -- please don't ask
me abo
On Thu, Jun 1, 2017 at 1:46 PM, Harald Schilly wrote:
> On Thu, Jun 1, 2017 at 9:02 AM, Dima Pasechnik wrote:
>> By the way, this example does work on SMC, so they must be doing something
>> non-standard here.
>> What is that?
>
> Hi, you need to be more precise, since CoCalc has a rather large
>
On Thu, Jun 1, 2017 at 9:02 AM, Dima Pasechnik wrote:
> By the way, this example does work on SMC, so they must be doing something
> non-standard here.
> What is that?
Hi, you need to be more precise, since CoCalc has a rather large
feature surface. In case you mean "sagews" files, they have noth
On 2017-06-01 02:13, Bernardo Feijoo wrote:
Then I tried to install again and the installation stopped with an error
about linbox. I just started it again and it seems to be progressing
past linbox, so I think it's making progress. I'm just gonna keep trying.
This suggests a hardware problem of
On Wednesday, May 31, 2017 at 2:24:55 PM UTC+1, Nicolas M. Thiéry wrote:
>
>Hi,
>
> I am investigating this. Current status:
>
> Remember that graphs can be latex rendered in two ways: either by
> having Sage produce tikz manually (1), or through dot2tex (2). For
> general graphs, the
18 matches
Mail list logo
