# Revision history [back]

I'm not sure whether this will work per se, but sage -sh is referring to quitting Sage and then starting it again from the command line with the -sh flag.

Everything after here didn't seem to work the way it should. I'm not sure what's going on. Mabe you really do have to install dot2tex 'manually'.

----------------------------------------------------------------------
| Sage Version 4.7.2, Release Date: 2011-10-29                       |
| Type notebook() for the GUI, and license() for information.        |
----------------------------------------------------------------------
sage: B=CrystalOfTableaux(['A',2],shape=[2,1])
sage: view(B)
dot2tex not available.  Install after running 'sage -sh'
sage:
Exiting Sage (CPU time 0m0.13s, Wall time 1m20.10s).
new-host-2:$sage -sh Starting subshell with Sage environment variables set. Be sure to exit when you are done and do not do anything with other copies of Sage! Bypassing shell configuration files ... SAGE_ROOT=/Users/.../sage-4.7.2 (sage subshell) new-host-2:$


So presumably then you would install it.

Except, as you point out, this is now an optional package. So I do sage -i dot2tex, restart, and get...

----------------------------------------------------------------------
| Sage Version 4.7.2, Release Date: 2011-10-29                       |
| Type notebook() for the GUI, and license() for information.        |
----------------------------------------------------------------------
sage: B=CrystalOfTableaux(['A',2],shape=[2,1])
ERROR    Could not locate Graphviz binaries
ERROR    Failed to create xdotdata. Is Graphviz installed?
ERROR    Failed to parse the input data. Is it a valid dot file?
Try to input xdot data directly. Example:
dot -Txdot file.dot | dot2tex > file.tex

If this does not work, check that you have an updated version of PyParsing and
Graphviz. Users have reported problems with old versions. You can also run
dot2tex in debug mode using the --debug option:
dot2tex --debug file.dot
A file dot2tex.log will be written to the current directory with detailed
information useful for debugging.


Huh. So your problems are probably not at an end at this point. I'm sorry I can't help further!