Search bar offers the following options:
Term presence. The below example searches for documents that
must contain “foo”, might contain “bar” and must not contain “baz”:
+foo bar -baz
Wildcards. The below example searches for documents with words beginning with “foo”:
Search in specific fields. The following search matches all objects
in "twisted.mail" that matches “search”:
Possible fields: 'name', 'qname' (fully qualified name), 'docstring', and 'kind'. Last two fields are only applicable if "search in docstrings" is enabled.
Fuzzy matches. The following search matches all documents
that have a word within 1 edit distance of “foo”:
Results provided by Lunr.js
Windows Process Management, used with reactor.spawnProcess
||A process that integrates with the Twisted event loop.|
||Look for a #! line, and return the value following the #! if one exists, or None if this file is not a script.|
||Determine if a pywintypes.error is telling us that the given process is 'not a valid win32 application', i.e. not a PE format executable.|
Look for a #! line, and return the value following the #! if one exists, or None if this file is not a script.
I don't know if there are any conventions for quoting in Windows shebang lines, so this doesn't support any; therefore, you may not pass any arguments to scripts invoked as filters. That's probably wrong, so if somebody knows more about the cultural expectations on Windows, please feel free to fix.
This shebang line support was added in support of the CGI tests; appropriately enough, I determined that shebang lines are culturally accepted in the Windows world through this page:
|filename||str representing a filename|
|a str representing another filename.|