BUG: Explorer plugin search with Everything about flow.launcher HOT 5 OPEN

Why are you using a space for the filespec after the folder? C:\downloads\*.jpg will find those files

from flow.launcher.

Why are you using a space for the filespec after the folder? C:\downloads\*.jpg will find those files

But why it shouldn't work? I expected consistency in searching with Everything and Everything in Explorer plugin. I believe C:\downloads\*.jpg is an example of default Windows masked search, while you can use C:\downloads\ *.jpg in Everything. As stated in Everything docs, space used as AND keyword to search for right part and left one, in my example C:\downloads\ is part of the path and *.jpg is file name, and they are combined with logical AND (space). There is a lot of non consistent behavior between Everything and in app plugin - you also can't use something like C:\downloads\ regex:^read

The reason I liked the idea of using Everything with Explorer plugin was because Everything has very convenient search for me. But it's troubling as I can't use the same thing in Explorer plugin even though I selected Everything everywhere in the settings.

And I hope you can agree with me that the same search not working in plugin is not very ideal thing.

from flow.launcher.

Flow handles spaces differently to identify keywords and arguments so as to trigger plugins, therefor any functionality of Everything that works with spaces will not work here. I'm not a core developer though so happy for one of them to jump in and confirm or offer alternatives.

from flow.launcher.

Flow handles spaces differently to identify keywords and arguments so as to trigger plugins, therefor any functionality of Everything that works with spaces will not work here. I'm not a core developer though so happy for one of them to jump in and confirm or offer alternatives.

Thanks though for your answer
Yes, me too. I can understand that Flow might handle spaces differently. But even if so, in that particular case I think there is no problem to make space work as in Everything (though I'm also not a dev here). On screenshots above I can tell that plugin recognized which one it should trigger, even with space, but again it "feels" like it's trying to use "default" search instead of Everything (but maybe I'm wrong).
Would be exciting to see if one of core devs can clarify this situation, and maybe there is a way to make this work consistently.

from flow.launcher.