Option to use more flexible keyword searching #28
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- also avoids issue with US title search url outside of US
jmeosbn
force-pushed
the
pull-requests/use-keyword-search
branch
2 times, most recently
from
069c6cf to
d1acce0
Compare
Author
|
Moving to #23 due as common code |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been having better results using
advsearchKeywordssearch instead of explicitly specifying a title search (which is much more strict and fails on things like numbers prefixed etc.). Author can still be specified which results in a more flexible title search still sensibly constrained when author known.Nice side effect is that
advsearchKeywords=survives when searching the.comsite from outside the US - unliketitle=.