1299, distinct: breaks updates in current window

[therube]

1299, distinct: breaks updates in current window


create files; red.txt blue.txt
search; <red | blue> ext:txt distinct:
copy red.txt redX.txt
copy blue.txt blueX.txt

results: ([still] only) red.txt & blue.txt
(open new window, & all four expected files are found)


(below, i started with: <1234 | 5678> ext:exe distinct:, but, oh well)

Code: Select all

Everything
Version 1.5.0.1299a (x86)
Windows NT 6.1
Processors 4
IsAdmin 0
AppData 0
Service 1
cmdline .\everything.exe  -instance 15
SetActiveWindow failed 00000000
WM_ACTIVATE 00000000 00000000, lastfocus 00310cdc, current focus 00310cdc
add nav <1234 | 5678> ext:exe distinct:
WM_ACTIVATE 00000001 00000000, lastfocus 00310cdc, current focus 00000000
FOCUS 0
FOCUS restore
add nav <1234 | 5678> ext:exe distinct:
WM_ACTIVATE 00000000 00000000, lastfocus 00310cdc, current focus 00310cdc
add nav <1234 | 5678> ext:exe distinct:
READ 8
READ 4
PIPE READ 3 12
update m 6 12e84630
READ 8
update index T:
PIPE WRITE 34 52
READ 8
READ 392
PIPE READ 0 400
READ 8
USN CREATE 1234 - Copy.exe
USN DATA_EXTEND CREATE 1234 - Copy.exe
USN BASIC_INFO_CHANGE DATA_EXTEND CREATE 1234 - Copy.exe
USN BASIC_INFO_CHANGE CLOSE DATA_EXTEND CREATE 1234 - Copy.exe
PIPE WRITE 34 52
READ 8
READ 8
PIPE READ 0 16
READ 8
read usn journal T: in 0.005096 seconds
PIPE WRITE 35 20
READ 8
READ 79
PIPE READ 0 87
PIPE WRITE 35 20
READ 8
READ 51
PIPE READ 0 59
READ 8
updated T: in 0.001834 seconds
resume ntfs monitor 6
PIPE WRITE 33 52
DB_WAIT: _db_journal_notification_event_proc waiting for _db_monitor_ntfs_proces
s_fd_update_events_thread_proc...
processed 1 usn records in 0.000267 seconds
READ 8
PIPE READ 0 8
DB_WAIT: _db_journal_notification_event_proc waited 0.001210 seconds
READ 8
processed 2 usn records in 0.000239 seconds
DB_WAIT: _db_monitor_process_fd_update_event_finished_event_proc waiting for _db
_monitor_ntfs_process_fd_update_events_thread_proc...
DB_WAIT: _db_monitor_process_fd_update_event_finished_event_proc waited 0.000214
 seconds
READ 8
READ 4
PIPE READ 3 12
update m 6 12e84630
READ 8
update index T:
PIPE WRITE 34 52
READ 8
READ 392
PIPE READ 0 400
USN CREATE 5678 - Copy.exe
READ 8
USN DATA_EXTEND CREATE 5678 - Copy.exe
USN BASIC_INFO_CHANGE DATA_EXTEND CREATE 5678 - Copy.exe
USN BASIC_INFO_CHANGE CLOSE DATA_EXTEND CREATE 5678 - Copy.exe
PIPE WRITE 34 52
READ 8
READ 8
PIPE READ 0 16
READ 8
read usn journal T: in 0.005692 seconds
PIPE WRITE 35 20
READ 8
READ 79
PIPE READ 0 87
PIPE WRITE 35 20
READ 8
READ 51
PIPE READ 0 59
READ 8
updated T: in 0.001665 seconds
resume ntfs monitor 6
PIPE WRITE 33 52
DB_WAIT: _db_journal_notification_event_proc waiting for _db_monitor_ntfs_proces
s_fd_update_events_thread_proc...
processed 1 usn records in 0.000316 seconds
READ 8
PIPE READ 0 8
DB_WAIT: _db_journal_notification_event_proc waited 0.001153 seconds
READ 8
processed 2 usn records in 0.000140 seconds
DB_WAIT: _db_monitor_process_fd_update_event_finished_event_proc waiting for _db
_monitor_ntfs_process_fd_update_events_thread_proc...
DB_WAIT: _db_monitor_process_fd_update_event_finished_event_proc waited 0.000192
 seconds
WM_ACTIVATE 00000001 00000000, lastfocus 00310cdc, current focus 00000000
FOCUS 0
FOCUS restore
add nav <1234 | 5678> ext:exe distinct:
WM_ACTIVATE 00000000 00000000, lastfocus 00310cdc, current focus 00310cdc
add nav <1234 | 5678> ext:exe distinct:

[raccoon]

1299a. - improved dupe: by no longer adding new results to avoid confusion.

I personally think that pausing should, instead, be a global on/off toggle, and not baked into specific functions. If I want to pause monitoring / adding new results, I should be able to slap the F9 key to toggle this behavior based on my own needs. Or the syntax "dupe: pause:"

[void]

Technically the results are not paused, results will be removed if they are deleted or renamed.

A dupe: search will simply ignore adding new results as it's not really feasible to maintain the results in real-time.

Previously, Everything would ignore the dupe command for new results.
New results would be added if they passed all other search filters.
This was causing confusion as the new results do not match the dupe command.

Change the search slightly (add a space to the end of the search or toggle match case) to force Everything to perform a requery.

[raccoon]

Ah, I see. The new results weren't trickling through the dupe/unique sort filter too.

[therube]

Oh, OK, thanks.