I was doing a search in my "bin" directory, looking for a script that contains a certain word.

In this "bin" directory, there are script files with no extension that are purely text. There are also binary executables in this directory with no extension.

In Tools->Editing->Search, the help for "Exclude binary files" states: "automatically exclude known binary file extensions". However, "no extension" files can mean binary or not binary in my "bin" directory. As a result, even though I have "exclude binary files" checked, I do see undesired search results of binary files that have no extension.

It would be nice if this "exclude binary files" could detect that a file is binary (for example, has characters in a certain byte range) and automatically excludes them from search results instead of relying on the extension, which is not useful in this example.

If you specify <Binary Files> in your excludes (<Default Excludes> contains <Binary Files> by default), additional logic will occur to exclude files that contain binary data. The algorithm used isn't amazing but it works quite well in practice. For example, this algorithm may or may not skip vrestore.slk because it contains a bit of binary data. It only looks at the first 2k of the file and only considers certain low bytes as binary. Files with text BOM markers are always considered non-binary (Utf-8, Utf-16, Utf-32).

At the moment, this additional logic doesn't support the "List filenames only" or "List current context" options.