Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve the documentation of show #370

Closed
williamstein opened this issue May 19, 2007 · 2 comments
Closed

improve the documentation of show #370

williamstein opened this issue May 19, 2007 · 2 comments

Comments

@williamstein
Copy link
Contributor

> One suggestion I have arising from my problems is that the
> documentation for the show command be improved.  It is a very
> important function for most users.

Agreed -- the documentation for show now is terrible.  It doesn't
even mention that it can be used to show the typeset version of
an object!

William

Component: user interface

Issue created by migration from https://trac.sagemath.org/ticket/370

@williamstein williamstein self-assigned this May 19, 2007
@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-2.9.1 milestone Sep 10, 2007
@mwhansen
Copy link
Contributor

comment:2

What is the status of this? Here is the current documentation when doing show?

        Show a graphics object x.
    
        OPTIONAL INPUT:
            filename -- (default: None) string
    
        SOME OF THESE MAY APPLY:
            dpi -- dots per inch
            figsize -- [width, height] (same for square aspect)
            axes -- (default: True)
            fontsize -- positive integer
            frame -- (default: False) draw a MATLAB-like frame around the image
    
        EXAMPLES:
            sage: show(graphs(3))
            sage: show(list(graphs(3)))

@malb
Copy link
Member

malb commented Apr 1, 2008

comment:3

Unless the request is specified, I'm all for closing it.

[13:19] <mabshoff> malb: what is your take on #370 ?
[13:19] <malb> it looks alright
[13:20] <mabshoff> If you also think it should be closed as fixed please do so.

@malb malb closed this as completed Apr 1, 2008
tobiasdiez pushed a commit to tobiasdiez/sage that referenced this issue Feb 22, 2024
* Add C++ compiler if the language specified in one of the ext_modules is C++

* Refactoring with improvements to search for fortran or c++ compilers

* improve fortran search
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants