Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Discussion related to "Everything" 1.5 Alpha.
Post Reply
anttin
Posts: 7
Joined: Thu Apr 13, 2023 1:20 pm

Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by anttin »

Hi!
Everything 1.5 has been working excellent but I noticed that something went wrong or some logic changed after 1367a.

When I use search for n: or t: it gives files from ALL drives :o
I do not have any filters that have macros n or t.
I also forced rescan, same result. N: is internal drive and T: is network share and they work normally elsewhere and Windows does not report any problems with them and in 1367a they work as expected.
Any other drive letter give the correct result, network drive or internal.

The change happened with 1368a and still exists in 1369a.
I had to revert back to 1367a.

Can you please fix it soon :)
horst.epp
Posts: 1431
Joined: Fri Apr 04, 2014 3:24 pm

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by horst.epp »

Confirmed for the drive letters N: and T:
I get results for C: in this case.
I don't have such drives and no macros or filters named like these drives.
______________________________________________________
Windows 11 Home x64 Version 23H2 (OS Build 22631.3155)
Everything 1.5.0.1368a (x64), Everything Toolbar 1.3.2
nikov
Posts: 131
Joined: Fri Dec 24, 2021 10:31 am

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by nikov »

Happening. Maybe it behaves as if N: is replaced with the character 0 and T: is replaced with empty.
therube
Posts: 4883
Joined: Thu Sep 03, 2009 6:48 pm

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by therube »

(I'll just note that as I also have a T: drive, I'll wait on this.)
void
Developer
Posts: 16452
Joined: Fri Oct 16, 2009 11:31 pm

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by void »

Thank you for the issue report.

The issue is caused by the new T and N preprocessor functions.

I will have this fixed shortly..

Sorry for the inconvenience.
void
Developer
Posts: 16452
Joined: Fri Oct 16, 2009 11:31 pm

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by void »

Everything 1.5.0.1370a fixes an issue with searching for n: and t: drives.
anttin
Posts: 7
Joined: Thu Apr 13, 2023 1:20 pm

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by anttin »

Excellent and incredibly fast work again, now it works perfectly again :mrgreen:

Thank you!
nikov
Posts: 131
Joined: Fri Dec 24, 2021 10:31 am

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by nikov »

Not happening anymore.
Thank you for the fix and quick speed.

Also, what are/were those T and N preprocessor functions? What is their status now? Are they removed or renamed?
void
Developer
Posts: 16452
Joined: Fri Oct 16, 2009 11:31 pm

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by void »

They are preprocessor functions for converting values to text/numbers:

[t:]
[n:]



They still exist.
However, only the following syntax is supported:
[t:"abc"]
[n:123]

#[t:"abc"#]:
#[n:123#]:
nikov
Posts: 131
Joined: Fri Dec 24, 2021 10:31 am

Re: Something went wrong after 1367a (and still same 1369a), certain drive letters give all drives :o

Post by nikov »

Thank you, nice to know.
Post Reply