#18289: Revert the changes that #17821 made to graph/
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.7
Component: graph theory | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: Nathann Cohen
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/graph_preference | 8372aaa58ba5226a96fcbf5e9c609743cb9411ce
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
Replying to [comment:56 mantepse]:
> Is there a difference between `latex(g)` and `g.__latex__`? What would
be the point of having $G_{123}$ as output? At least for me it would be
completely useless.
* `latex(g)` just calls `g._latex_()`, so they are equivalent
* We should certainly have a way to get the tikz code.
* The problem is that if you click the "typeset" checkbox in SageNB then
it calls `latex()` for every output. But typesetting tikz often fails,
resulting in a quite broken notebook. For large-ish graphs we shouldn't go
that route in the displayhook.
The two logical options are either
* move the tikz output, something like `graph.plot(format='tikz')`, or
* not call `graph._latex_()` when typesetting output, for example
implementing a different latex view it in `graph._rich_repr_()`
--
Ticket URL: <http://trac.sagemath.org/ticket/18289#comment:62>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
