Not working as specified

[markcmiller86]

Am testing features here and have some observations...

• Each time I want to adjust a search string, the pop-up window begins with empty text, even though the RTD search text field shows the text I last entered (or there-abouts...it winds up being subtley altered. For example any + is removed).
• Searching for endian +-silo returns 9 pages which tells me its return pages that include either endian or silo and not pages that contain endian but do not contain silo.
• + operator seems wholly ignored. In fact, it gets removed when RTD echos the search string back
• All these search strings return the same result chunk fortran, chunk +fortran chunk + fortran, chunk | fortran
• -silo returns all pages (silo is used on some pages).

So, either I am wholly mis-understanding how this is supposed to work or the search functionality is not working as documented.

[stsewd]

The first thing is a known problem #58.

The second and third are related to rtd itself, not the extension. We use https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-simple-query-string-query.html#simple-query-string-syntax, so you need to escape those queries.

[stsewd]

Also, if you are really trying to use the + or | operators, we always run all queries with those operands already.

[markcmiller86]

Apologies but I'm confused by your response.

Indeed, I am not trying to search for literal + or | or - as characters in the search results. I am trying to use those character as operators as described in the simple query string documentation you reference which explicitly states...

To use one of these characters literally, escape it with a preceding backslash ().

which I am NOT trying to do. I really want to test the behavior of those query operators and so far, my tests don't seem to be indicating those operators are really working.

Neither do they appear to work with the examples provided here. Trying it auto* redirect* (hit enter), RTD says 46 pages and auto* +-redirect* returns 50 pages). How can that be correct? The 2nd should be more restrictive than the 1rst.

Finally escaping the operators makes no difference. Is as if I didn't type them at all. Same behavior in Safari, Chrome and Firefox. If you'd like, I can upload video of behavior. Maybe from that you can tell me what I am doing wrong?