Remember find mode between sessions

[admin]

Maybe "Redo last search on startup"?

Oh yes, that's good! Almost... because the "last search" must not actually be active when the app is closed. I already hear some of you folks complaining about the ambiguity...

[j_c_hallgren]

My basis for that phrase was YOUR text in help file describing "remember find" option details...
So..."redo last active search on startup"? Or "last completed"? I'm not sure if either might be more accurate, just trying to inspire thoughts!

[admin]

For me "Redo last search on startup" is perfecto!

[jacky]

I've never used the "Remember find" option because I prefer not having some things done automatically on startup...and I suspect many users are similar...but they may not be posting here...the 'silent majority' maybe?

That's what I feared and why I double-asked... if I take it out it will be TRUE internally always and forever...

hmm... or no one is saying anything cause they're not against it

I personnally don't think it would fall into the "having some things done automatically on startup" category. What I mean is, unless I got it wrong, it wouldn't cause a search on startup unless
a/ you closed XY on a Finding tab
b/ you have "Save settings on exit" enabled, which means you want it to be doing stuff automaticly on startup. You want XY to start the way it was close, ie with search results on, so let's do the search! (you can stop it anytime anyways)
If you don' t have this option (Save settings on exit) cause you want XY to always start the same, that won't change!

"Redo last search on startup" sounds somewhat "misleading" to me, as again it would only be true IF you save settings on exit.... or else it's false. It won't apply, or to the search run when you last saved your settings, not the last search!
EDIT: I mean seriously, "Redo last search on startup" basicaly says the same but with different words as "Remember Find mode between sessions". So its confusing-side is still there....

[RalphM]

For me "Redo last search on startup" is perfecto!

I'm with you.

[admin]

... "Redo last search on startup" sounds somewhat "misleading" to me, as again it would only be true IF you save settings on exit.... or else it's false. It won't apply, or to the search run when you last saved your settings, not the last search!

There is a possible use of "Redo..."=ON and "Save on Exit"=OFF: simply if you always want XYplorer to start with the same search (no matter how/where you closed it last time). It's the last stored search.

Maybe a better caption -- avoiding that possibly misleading "last" -- would be "Allow search on startup". But that's misleading in other ways...

What about "No search on startup"? As i said before, the original impulse leading to that option was to avoid searches on startup, not to allow them (starting as closed before is just normal/default for XY).

[j_c_hallgren]

The only downside I see by going 'negative' (No search) is that people like me would then have to specifically activate that option, unless having it checked would become the default on re/installation.

[admin]

The only downside I see by going 'negative' (No search) is that people like me would then have to specifically activate that option, unless having it checked would become the default on re/installation.

I see exactly this as an advantage! It's one of XY's virtues that it can do this. Show me another file manager that can run a stored search on startup. One of XY's claims is "Start up as you closed down"...

[admin]

EDIT: I mean seriously, "Redo last search on startup" basicaly says the same but with different words as "Remember Find mode between sessions". So its confusing-side is still there....

So, what do you think of "No search on startup"?

[admin]

I've never used the "Remember find" option because I prefer not having some things done automatically on startup...and I suspect many users are similar...but they may not be posting here...the 'silent majority' maybe?

Hm. I must come back to this again. Technically the differences between browsing and searching are only these two:
(1) searching is optionally recursive (-> list tends to get larger)
(2) searching is filtered (-> list tends to get smaller)

Both, browsing and searching are things "done automatically on startup". So, since we have the possibility to ESC a search on startup if it's getting to longish, I really don't see any good reason for having that checkbox anymore! You might look at it even this way: if you happen to startup on a very large directory, there is no ESC to stop the browsing. So you might be off worse with a browse than with a search on startup!

[jacky]

Both, browsing and searching are things "done automatically on startup". So, since we have the possibility to ESC a search on startup if it's getting to longish, I really don't see any good reason for having that checkbox anymore!

Agreed!

[j_c_hallgren]

For people like me, (who would prefer to not have to use ESC to stop search no matter how I left XY last time), having a way within the INI file to trigger this ability would be nice...this would keep it out of normal checkboxes but still provide option for us folks...

[admin]

For people like me, (who would prefer to not have to use ESC to stop search no matter how I left XY last time), having a way within the INI file to trigger this ability would be nice...this would keep it out of normal checkboxes but still provide option for us folks...

Not possible -- this option was an anomaly that I'm happy it's gone. I could throw away a whole lot of extra code.
Here are 2 workarounds:
- Save settings on exit -> OFF
- Don't exit.

[jacky]

Well:

I personally don't do "save on exit" but manually do a save whenever I've changed some option that I want to keep

So I'm guessing you won't have to face a search at startup ever, as long as you remember to save your settings while being on a browsing tab.

- Don't exit.

hehe.. though that can't be done, one have to update to the next beta every so often, so exiting XY has to be done at times

[pissant]

I'm not trying to be snarky here--really, I'm not--but I don't have time for word games, or to figure out the many nuances to XY's behavior regarding search tabs.

What I simply want to know: Is there some way (currently) that I can make the search settings not be remembered between runs?

I often use the Contained Text search feature. But these are highly-specific searches, and I never want to do it more than once. Yet whenever I do a Contained Text search, the Contained Text is remembered between runs, as is the Text search option itself. This tends to be really inconvenient when overlooked upon starting a new search (and inadvertently searching for the same text again).