#13064: The documentation should search methods in classes
------------------------------------+---------------------------------------
Reporter: ppurka | Owner: mvngu
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.6
Component: documentation | Resolution:
Keywords: documentation | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Travis Scrimshaw | Merged in:
Dependencies: | Stopgaps:
------------------------------------+---------------------------------------
Comment (by jhpalmieri):
Those `search_*` functions are only available when you're running Sage,
while the documentation search page just needs the build documentation —
no need for Sage to be running. So that's one reason why they're not
integrated, and probably why they shouldn't be.
I'm imagining text like "You can also run `search_src(...)` from while
running Sage to search the source code. You can also browse the source
code by running `hg_sage.serve()` from Sage."
Re `search_def('blah')`: it is like `search_src('blah')`, but it restricts
its search to lines of the form `def blah` or `cdef blah`, so it sees both
functions and methods which contain 'blah' in their name.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13064#comment:10>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
