-
-
Notifications
You must be signed in to change notification settings - Fork 510
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
search_doc does not find phrases across multiple lines #7313
Comments
comment:1
Please use summaries that actually describe the problem. |
comment:2
Got it !! I mixed Sage-devel and TRAC :-) |
Author: John Palmieri |
comment:3
Here's a patch implementing a "multiline" keyword for searches, so you can do
(With multiline searches, it doesn't return line numbers, just the file names.) |
Attachment: trac_7313-multiline.patch.gz depends on #7018 |
comment:4
Tested this on sage-4.3.2.alpha0 with trac_7313-multiline.patch Look for occurrences of "Pseudo". We find two occurrences.
Next, search for a multiline ocurrence of "Pseudo-Palindromes" which should occur over lines 2655-2656 in word.py according to the last search. (Note: the 2nd line is prefixed with whitespace)
Not sure if the problem is due to the patch mentioned in #7018 needs including and updating for alpha0, or this ticket needs more work or theres something Ive missed. |
comment:5
(The patch from #7018 is already part of 4.3.2.alpha0, which is probably why applying it gave you errors.) Since the string "Pseudo-Palindromes" doesn't appear, I think it is correct that searching for it returns nothing. Try this instead:
Actually, though, Pseudo- and Palindromes appear on the same line, so this isn't the best test case. How about
|
Reviewer: Mitesh Patel |
comment:6
Quick note: |
comment:7
(Confirming positive review).
|
Merged: sage-4.3.3.alpha0 |
Changed reviewer from Mitesh Patel to Ross Kyprianou, Mitesh Patel |
Hello !!!
Out of curiosity, I tried to look for a function I knew in Sage :
I understand the current way to look for things in the doc is to grep it, and that for some reason we may need to keep our lines short ( less than 80 characters or so ).. I also understand that finding another way to search the doc ( if there is none available already ) may be some big amount of work. Even though, this really isn't the expected behaviour of the function, and I think we should do something about it.
Nathann
CC: @dandrake
Component: documentation
Author: John Palmieri
Reviewer: Ross Kyprianou, Mitesh Patel
Merged: sage-4.3.3.alpha0
Issue created by migration from https://trac.sagemath.org/ticket/7313
The text was updated successfully, but these errors were encountered: