Losing search queries on app crash or electricity blackout

Found a bug in "Everything"? report it here
Post Reply
Cleoss
Posts: 27
Joined: Wed Mar 07, 2018 7:10 am

Losing search queries on app crash or electricity blackout

Post by Cleoss » Wed Mar 07, 2018 7:24 pm

Hi, Void!

I don't know is it a bug, or just a feature. But I live in Donbass (we have the war nearby) and have blackouts few times per week. And with a pass of time I've noticed that Everything can't remember anything from my search history if I don't reopen it (and I never do it coz I'm using a sleep mode in spite of reboots). So I always loose my search entries and have small size of autosuggestions.

Now I'm using a script for Clickermann (automation tool) to relaunch Everything. Hope this can help somebody, and also I hope that Everything 1.5 will save the queries once u input 'em, but NOT on exit.

Here's the script I use:

Code: Select all

// 18-Jan-2018
#name "EvytnReld"
#autorun
//#include "alt-qs.cms"
define($path,"E:\port\PortableApps\~~etc\Everything-1.4.1.877.x64\Everything.exe")
$hwnd1 = WNDFIND ("Everything")

//while(1)
   KEYDOWN (#ctrl)
   //A_KEYpress (#Q, $hwnd1)
   hset($hwnd1,1)
   KEYpress (#Q)
   hset($hwnd1,0)
   KEYUP (#ctrl)
   wait(15)
   execute($path)
//   wait(5)
//   KEYDOWN (#win)
//   KEYpress (#down)
//   KEYUP (#win)
//   //wait(5)
   wait(0+4*3600)

//end_cyc

//halt
And I added this script to System autorun with TaskSheduler.

Cleoss
Posts: 27
Joined: Wed Mar 07, 2018 7:10 am

Re: Losing search queries on app crash or electricity blackout

Post by Cleoss » Wed Mar 07, 2018 7:49 pm

Oh, I just have read out this (Night builds), and isn't a fix called "[886] Fixed an issue when shutting down Everything would cause it to miss changes" my one? Seems to be not, but maybe it put an effect on it, and maybe this fix will help me?

void
Site Admin
Posts: 4851
Joined: Fri Oct 16, 2009 11:31 pm

Re: Losing search queries on app crash or electricity blackout

Post by void » Fri Mar 09, 2018 7:58 am

Search history is saved to disk when one of the following occurs:
  • An Everything search window is closed.
  • The Windows session ends (user log off).
  • You exit Everything.
  • You make a change in the Search History Organizer.

I can see this being an issue if you never close your Everything search window, I'll consider saving the search history to disk more often.

Thanks for the bug report.
[886] Fixed an issue when shutting down Everything would cause it to miss changes
This is unrelated to search history.
Only file system changes detected by Everything was effected.

NotNull
Posts: 1405
Joined: Wed May 24, 2017 9:22 pm

Re: Losing search queries on app crash or electricity blackout

Post by NotNull » Fri Mar 09, 2018 7:03 pm

void wrote: I can see this being an issue if you never close your Everything search window, I'll consider saving the search history to disk more often.
Or add saving INI / search history / run history to the Everything.exe -update command?

Cleoss
Posts: 27
Joined: Wed Mar 07, 2018 7:10 am

Re: Losing search queries on app crash or electricity blackout

Post by Cleoss » Fri Mar 09, 2018 7:21 pm

NotNull wrote:Or add saving INI / search history / run history to the Everything.exe -update command?
Yes, you're right, I've tested this cli-option and found that it updates only db, NOT the ini+sets :(

NotNull
Posts: 1405
Joined: Wed May 24, 2017 9:22 pm

Re: Losing search queries on app crash or electricity blackout

Post by NotNull » Fri Mar 09, 2018 7:26 pm

That's why I suggested it :D
In your case, this everything.exe -update can be easily scheduled to run (no need to close the running Everything).

Cleoss
Posts: 27
Joined: Wed Mar 07, 2018 7:10 am

Re: Losing search queries on app crash or electricity blackout

Post by Cleoss » Fri Mar 09, 2018 7:49 pm

NotNull wrote:In your case, this "everything.exe -update" can be easily scheduled to run (no need to close the running Everything).
I wait this fix much :) This also mean that I won't lose a scrolling position in a search window any more during those relaunches. Sure, we can use "-focus-last-run-result" or "-select filename.ext" options, but how we can define a current position filename (to restore it on next-time launch)? :roll: Oh we can define the hotkey for File > Copy Path to Clipboard, copy the selected filename with it and store this name to use it in command-line later.

Post Reply