Find files: duplicate paths when connecting Everyhting

[Fla$her]

After connecting to other computers, replacing the drive with the same letter, Everyhting adds similar paths to the existing ones in the database.
As a result, the number of duplicates is growing. Please force TC to check the found data and exclude duplicates before output.

[nsp]

This is for me more an issue of Everything than an issue of TC. TC do not ask for lookup to Everything.
If you have external drive you unplug, by default everything will continue to gives result of - non existent - drive. Same story and TC do not have anything to do with IT.

[Fla$her]

2nsp
TC generates its list from the received data, so it is responsible for a false output.
If non-existent single paths are displayed, this is one thing, you can still live with it, but when TC returns matching paths even when searching for duplicates, then this is not good at all.

[Horst.Epp]

Configure your Eveything and ask void for the correct settings to avaoid this.
Its not TCs job to verify because it may lead to long delays for non existant networks shares.

[Fla$her]

Configure your Eveything and ask void for the correct settings to avaoid this.

Are you talking about removing disconnected local volumes from the indexing list? This is not profitable for me, since a portable assembly is used.

Its not TCs job to verify because it may lead to long delays for non existant networks shares.

I'm primarily interested in local files. For network shares, can be come up with an ini key.

[nsp]

You should find/ask option in Everything to not return non-existent files !
Read Help and learn how to use everything to have "up to date index" for all the drives you want to search. In the help about NTFS and how to remove drive when disconnecting, ...
TC do what you ask for:

• use Everything as file provider instead of the Disk.
• If your concern is to have TC searching on Drives, just un-tick Everything.

[Fla$her]

You should find/ask option in Everything to not return non-existent files !

Why am I, and not the author of the program who implemented this functionality?

Read Help and learn how to use everything to have "up to date index" for all the drives you want to search. In the help about NTFS and how to remove drive when disconnecting, ...

Why should I read help when I have all the options in front of my eyes? About deleting disks, I gave an explanation above.

TC do what you ask for:

• use Everything as file provider instead of the Disk.
• If your concern is to have TC searching on Drives, just un-tick Everything.

• On the contrary, I'm asking about something that doesn't exist yet.
• That's bad advice.

I would prefer to know the author's opinion.

[Dalai]

If TC would verify the result of each filename returned by Everything, it would kind of defeat the purpose of a very fast search, because checking for a file's existence also costs time (which gets worse if anti-virus software is involved).

Regards
Dalai

[tuska]

2Fla$her

If you want to get a quick solution to your problem, then I recommend you
- to write an email (support@voidtools.com) to the author of 'Everything'
  AND
- to send him a very detailed description *) of your problem.

*)
e.g.

1. Everything Version
   1. Everything 1.5 Alpha
      Everything 1.4.1 Beta Nightly Builds
      Everything 1.4
2. Windows Version
   Windows 11
   Windows 10
   ...

[Fla$her]

2Dalai
By data checking, I didn't mean checking the existence of files in the system at all. It is enough to check for the presence of adjacent duplicate rows and exclude them from the list. This operation should take place much faster.

The output of identical paths should not be in the logic of TC, regardless of which program takes part in it.

2tuska
I'll think about it. But I don't really care about this problem in Everything itself, because it almost does not affect anything in the process of working with the program window, while in TC this influence is quite significant.
Besides, I doubt that the author of Everything will do anything. Rather, he will offer the same optionality that I called. Saving records for other disks in the program is definitely in demand, otherwise these options would not exist.

[ghisler(Author)]

I can confirm that "Everything" may return a file twice in search results, e.g. when a folder was added manually via settings and the drive itself was indexed too. Since I'm receiving the results in order "EVERYTHING_IPC_SORT_PATH_ASCENDING", which means that they are sorted by full path and name, it's very easy to detect and remove these duplicates because they are returned together in the list. Therefore I will remove such duplicates from the results.

[Fla$her]

it's very easy to detect and remove these duplicates because they are returned together in the list.

Exactly. That's what I mean. Thanks for not put this aside.

[ghisler(Author)]

Could you test it with RC4, please?

[Fla$her]

Fixed. Everything is fine. Thanks!

[Fla$her]

I have to return to this topic. The problem of eliminating duplicate paths has been solved, but the search for duplicates is still focused on the list before processing. I.e. if Everithing returned more than one match, then we will still see one element in the output, which is unacceptable.
Checking the quantity should be carried out after culling.