Stack Overflow Developer responsible for this bug here! I've been investigating a different way to retrieve the Posts-associated-with-a-Tag data, starting with the Newest-sorted data and, unfortunately, when I turned it on for a short duration on the Stack Overflow site it exhibited an incorrect behaviour which I hadn't seen in the testing that I had performed locally and on other sites.
The new code is behind a feature flag and so can be toggled on or off easily, which explains why the bug appeared and then disappeared and then briefly came back.
I'm confident that it is now working correctly (following a code deployment yesterday) and the flag is enabled again here (meta) and on the Stack Overflow site - so those sites are using the new code.
Thanks for reporting this bug and please accept my apologies for the inconvenience!
[cmd]
seems to pull the exact same results as searching forcmd is:q
now.[tag] is:q
still seems to pull the intended results, as a temporary work around for the moment.is:q
isn't a bug. You search for the term batch-file, not for the tag. To search for tag, you have to put[
before it and]
after it. The system do it for us automagically for the most popular tags, but it's not good idea to count on that behavior, better always enclose tags with the proper characters when searching.batch-file
did not appear in that question either! Only the case insensitive substringBATCH
/batch
. Does that mean the the search is treating the character-
always as a space or word separator?