Page 1 of 1
Let searches use the output of any plugin field as a value
Posted: 2022-05-02, 12:31 UTC
by jj42
This came up in another thread:
jj42 wrote: ↑2022-04-27, 11:13 UTC
Another idea that could be very powerful:
When defining searches, make it possible to use something like [=tc.path] (or any plugin field) as a value. This way you could compare two fields with "==" or "!=".
Also, there is a precedent that it could hopefully be done:
petermad wrote: ↑2022-04-27, 14:00 UTC
It is already possible in the Change attributes dialog to feed output from one plugin to another. So something along the same path for Find Files.
Re: Let searches use the output of any plugin field as a value
Posted: 2022-05-02, 15:55 UTC
by petermad
Suport+++
Re: Let searches use the output of any plugin field as a value
Posted: 2022-05-03, 12:52 UTC
by nsp
Support+++
Re: Let searches use the output of any plugin field as a value
Posted: 2022-05-03, 15:24 UTC
by ghisler(Author)
It would unfortunately break compatibility with older saved searches. It would also be difficult to handle when the search fields aren't text, or even use different types as source and target.