Question regarding using {dlgstring} in Opus 13 Beta with Everything 1.5

Discussion related to "Everything" 1.5 Alpha.
Post Reply
abr01
Posts: 89
Joined: Tue May 01, 2018 4:57 pm

Question regarding using {dlgstring} in Opus 13 Beta with Everything 1.5

Post by abr01 »

Following button in Opus 13 Beta command does not return any results. Using Opus' '+' query, adding content:search: works as expected. I suspect, that the curly brackets ar not compatible with Everything's syntax. Is there another way to handle this?

Set Focus=right
Find CLEAR QUERYENGINE=everythingglobal QUERY content:search:{dlgstring}
void
Developer
Posts: 16670
Joined: Fri Oct 16, 2009 11:31 pm

Re: Question regarding using {dlgstring} in Opus 13 Beta with Everything 1.5

Post by void »

Please check the received IPC request in the Everything Debug Console:
  • In Everything, from the Tools menu, under the Debug submenu, check Console.
IPC requests are shown in Cyan color.

What is the {dlgstring} from Opus? and what is received by Everything?
abr01
Posts: 89
Joined: Tue May 01, 2018 4:57 pm

Re: Question regarding using {dlgstring} in Opus 13 Beta with Everything 1.5

Post by abr01 »

Well, the {dlgstring} is the input, the search item, which is received.. All the other filters from Everything work fine in Opus 13 Beta, because they have predefined criteria, like file: dupe: dupesize: size:>500mb, no input needed. But in this case, like in my code example, it won't work at the moment, at least with the {dlgstring}. If i use the '+' command in Opus' Find As you Type, and add content:search: there, it works. So i wasn't sure, if the brackets clash with Everything's syntax, or the developers may have a look on their side, whether they can make this function work. At the moment i use their '+' FAYT mode, and append the content:search: part using some Autohotkey shortcut, which does the typing for me. About the IPC, i am not very technically skilled, but maybe the developers from GP Soft can make something of it. Thanks!
void
Developer
Posts: 16670
Joined: Fri Oct 16, 2009 11:31 pm

Re: Question regarding using {dlgstring} in Opus 13 Beta with Everything 1.5

Post by void »

it won't work at the moment, at least with the {dlgstring}
What is the exact request received by Everything shown in the debug console?
(please email to support@voidtools.com if you don't want to post here)

I wonder if it's a macro or the preprocessor or an operator breaking your content search..
abr01
Posts: 89
Joined: Tue May 01, 2018 4:57 pm

Re: Question regarding using {dlgstring} in Opus 13 Beta with Everything 1.5

Post by abr01 »

For example, i try to find the word 'cinema' in some text file, that woul be my input, what {dlgstring} is receiving in Opus. I am not sure, how Opus is communicating at that point with Everything, regarding the debugging process.
abr01
Posts: 89
Joined: Tue May 01, 2018 4:57 pm

Re: Question regarding using {dlgstring} in Opus 13 Beta with Everything 1.5

Post by abr01 »

In the meantime an user found the right syntax to make it work. So, the problem is solved. Here is the code that works:

@set query= {dlgstring}
Find CLEAR QUERYENGINE=everythingglobal QUERY content:{$query}


From the Opus forum.

https://resource.dopus.com/t/buttons-fo ... s/46094/24
Post Reply