[Solved] Search history does not save by search from Home in 1422b

[Herkules97]

In the Home section of the settings window one can set an automatic search every time a window is open.

This works fine at least up to 1386a, but now that I've added a new instance with the latest v1.5.0.1422b it doesn't save the search.

I could be blind, I see nothing in the ini from searching "history" to what could change it back. A missing setting?

Pressing enter key every time to save it would be tedious.

[therube]

Should be working.
All the "Home" Search: does is to set the .ini value of search=<search>.

Do you have (Tools | Options -> General ->) Search: set to Custom, with your wanted search set in the next field?

[Herkules97]

I took the ini from 1386a, if it's supposed to save a search on a new window maybe it's bugged from the ini not being fresh for 1422b.
Don't think I've had a bug utilising old inis for newer versions but there can always be a first.

Unless you misunderstand? Reads like you think it isn't searching..It just isn't saving it to history.

Maybe most don't want history of the automatic search to be saved, but I'd like to.

[void]

What is your Tools -> Options -> Home -> Search setting?

Session being restored? -a session restore would override this default search.
Tools -> Options -> Advanced -> new_window_command_line / tray_show_command_line / new_tab_command_line can override this default search.

Could you please send your Help -> troubleshooting information in a bug report.

[Herkules97]

What is your Tools -> Options -> Home -> Search setting?

Defaults except search being "Custom" with "Test" as the search

Session being restored? -a session restore would override this default search.

session_store_restore_last_closed_window was set to true.
False does nothing, though at least one 1386a instance has it set to false.
I also don't use session restores, but I do store the sessions just cause
Instances save just fine with the above setting true or false. Something to do with a change between 1412b and 1422b unrelated to user's own settings. Maybe something that would need to be exposed to the user to alter.

Tools -> Options -> Advanced -> new_window_command_line / tray_show_command_line / new_tab_command_line can override this default search.

The search isn't the issue, it searches just fine.
Also these 3 are empty.

Could you please send your Help -> troubleshooting information in a bug report.

Is it better here or in bug report? Here it would just be inside the post, I don't remember what you've said in the past but IIRC you did say one or the other was better.
Anyway this is a near fresh instance and it's doing the same thing. Only changed settings that were inconvenient and then one search history one that causes it to save any search, not just on full instance exit.

Everything 1.5.0.1422b (x64)
OS: Windows NT 10.0 19045 (x64)
Admin: 1
Service: 0 (disconnected / not installed)
Command line: -instance "Lazy auto-search test 1.5.0.1422b C9v2
Binary: C:\C9\Portables\EBV\EverythingVoidtools v1.5.0.1422b x64\Lazy auto-search test\Everything.exe
Profile: C:\C9\Portables\EBV\EverythingVoidtools v1.5.0.1422b x64\Lazy auto-search test\Everything-Lazy auto-search test 1.5.0.1422b C9v2.ini
Database: C:\C9\Portables\EBV\EverythingVoidtools v1.5.0.1422b x64\Lazy auto-search test\Everything-Lazy auto-search test 1.5.0.1422b C9v2.db
Instance: Lazy auto-search test 1.5.0.1422b C9v2
Base Address: 0x00007ff6f6460000

Config:
auto_include_fixed_volumes=0
auto_remove_offline_ntfs_volumes=0
search_as_you_type=0
search_history_add_on_listview_set_focus=0
search_history_save_on_change=1
columns=[{"name":"Name","width":256},{"name":"Path","width":256},{"name":"Size","width":96},{"name":"Date Modified","width":153}]

Policy:

Plugins:

Have you tried it with 1422b? Idk if 1421b and further back does it too, I went from 1386a to 1422b
I do have a 1411b instance but I don't use auto-search for it..But if I try that temporarily it works just fine.

[therube]

Maybe it has to do with running

Admin: 1

.
If you disable that, or if you test in a new Profile, without running "as Admin", does the setting then work as expected?

- does not appear to make a difference, with a quick test, here.
(I set the GUI to run "as Admin", only, i.e. not also the Service.)

"Custom" with "Test" as the search

Quit Everything & confirm that in .ini that search is set to,

search=Test

.


And that's weird isn't it.

Admin: 1
Service: 0 (disconnected / not installed)

Yet, under Config: it does NOT show, "run_as_admin=1" ?


I'll note that your Instance name does not have a closing ("), though that does not seem to make a difference.


Your Command line: does not have,

-isrunas

, which I do see on my end.
Don't know if that makes a difference? I'm running my Instance from a batch file, Everything -instance <name>.


I take it, that you are not actually indexing anything at this point in time (or at least are not updating the index)?

[void]

Is it better here or in bug report?

In a bug report or here is fine.
The troubleshooting information can contain unique volume GUIDs.
I'll remove these if you post them here.

Admin: 1

In your case, running as admin is fine.



I think I understand the issue now.
1417b and later no longer adds the initial home search to your search history.
The next update will add the initial search to your search history.

So if you set Tools -> Options -> Home -> Search to

test

,

test

will be in your search history when you start Everything.

[void]

Everything 1.5.0.1423b will now add the initial search to your search history and navigation history.

Everything 1.5.0.1423b also fixes an issue with the Organize Search History using the wrong default column widths.