Hot answers tagged

11

The term IndexString occurs as a part of the longer string m.IndexString("foo in the post you're searching for. For this reason, you need to use wildcards * to find this post. Indeed, when I try searching for user:1002260 *IndexString*, I see your post in the search results. Searching for user:1002260 *IndexString also works. Perhaps this has to do with ...


8

TL;DR. AND search by default is bad idea. I tried your original query, it also shocked me how that query was unable to find the question post. Then I spot a relevant thread (suggested by the "Related" section on the right column) and here is the link: A new search engine for Stack Exchange It has been emphasized that the search engine is doing AND ...


7

user: takes the numeric userid, not a name. E.g. you can search through your own posts with user:156151. When you don't use a numeric argument (such as user:FakeUserName), the filter is ignored entirely, as if you didn't enter a search at all. If we replaced user:fakeUsername with user:1234567890 you'd get zero results, even though there is no such user ...


7

You can find it in your network profile, it's one of the tabs there. Or you can use this direct link: https://stackexchange.com/users/current?tab=bookmarks. Here's how it looks like for me: As @ShadowWizard notes in the comments, it only shows the 150 highest scoring/newest/... bookmarked questions (depending on the tab). If you want a complete list, you'll ...


3

This issue has been solved: the search field and corresponding button are no longer shown on the search results page anymore; you have to use the one in the top bar instead.


2

If you want to search for a user on the basis of (part of) their username you can go to /users. Here is an entry field to search on username. Do note however that usernames are not unique, and can be changed from time to time.


Only top voted, non community-wiki answers of a minimum length are eligible