Right now, if you want to edit the default search query for FSRS optimisation/evaluation you need to type out the preset name yourself. I think most of the time you’ll be having the same preset and some modification like introduced:20/-tag:sometagname.
I have changed my query enough times that it’s getting exhausting to write out the whole thing myself, every time. My preset names can a bit complicated so it would be easier if I could just edit the default search query.
Is there a way we can gray out the default query but also to make it editable?
Oh, now that I go looking for it that’s how the default search query in Statistics screen work too.
So, given the precedent we can have something similar in deck options too?
Incorrect default search query? How so? That would involve changing the search query at the same time.
Actually, I’m now thinking if we should have something like preset:current like in the stats screen. That would also make typing things out easier but I guess it’s a different issue.
Having the FSRS query be editable would be an improvement (even if it would have the slight unfortunate tendency to encourage users to edit the default search, which they ordinarily will not need to). I agree that the closer we can get to mirroring the behavior of the other 2 similar search boxes, the better.
In Browse –
The window launches either with a foreground user-supplied default deck as the active displayed search, or with background instructions.
When the box is emptied, those same background instructions appear – and the window falls back on a deck:current search result (if I’m not mistaken).
In Stats –
The window launches with a foreground deck:current as the active displayed search.
When the box is emptied the background Search instruction appears – and the window falls back on a whole-collection search result. [The same as if the “collection” radio-button is selected.]
So, in the FSRS default query, we can’t exactly match either of those, but this would be a predictable analog –
The default could be a foreground preset:PresetName -is:suspended, since it will be the active search.
To avoid confusion, when the box is emptied, the background text should be the same default (preset:PresetName -is:suspended), since that is what FSRS will fall back on if nothing else is provided.
But unlike Browse and Stats – this box preserves the last-saved search after closing. So, if it is saved empty (default search as background) – should it open the next time with the default search as foreground, so it is editable again? Or should the box stay empty, and need a “restore” button to put the default search back in the foreground?
@Keks would probably like something different: no text means FSRS doesn’t optimise at all. Maybe show a pop-up asking people input a search term/restore when saving the preset or trying to optimise/evaluate with it.
My suggestion was for “no text” not to be an easy option. An emptied field would fall back on the default search – and display that as background text.
To prevent the preset from being optimized, I use -*
And as long as it remains possible, everything suits me.
We create a preset PresetName1 that gets a preset search:PresetName 1 -is:suspended after we rename the preset to PresetName2, it will have the preset search field:PresetName1 -is:suspended since it was not empty.
Try changing presets and optimise, you’ll be shown a pop-up saying you need to save the changes first before you’re able to optimise. Anki changes the search query after that.
I think we’d be having to do the same. Or you’re saying that’s not feasible here?
A cleaner UI is to use preset:current though (say, if someone wants to rename two presets to switch their names but don’t want to change the query).
