Leon

Thanks, that seems sensible! Something like "ab" (before everything else), "as" (after setup) and "af" (after flip) might also work. When editing or writing cards, another audio command I frequently...

Thanks for the detailed bug report and your proposed fixes! I prefer the format / insert solution because it relies just on some common and stable functions of Emacs. One...

While the bug seems to be occurring sometimes during my reviews with org 9.7, I have not been able to replicate it consistently. Org-fc now will write all of the...

Some of the last changes made to org-fc (support for multiple algorithms and refactoring the dashboard) were intended to ease the way for adding FSRS. There is an experimental implementation...

Wow, that's a very nice implementation! Regarding next step 1, to my understanding of FSRS (version 5) if we track the card data ourselves the FSRS card_id does not matter...

I think the optimizer works on (card_id, date, rating, duration) entries which could be computed from the existing review log format. In that case users could also optimize FSRS based...

> I'm not sure I understand. I'd thought the way optimization would work is that the user would pass all their review logs (for all positions) into the optimizer and...

What's missing to finish this? Just the function for writing review logs (I'd just use the same as SM2 and set box, interval and ease to null)? The python file...

In https://github.com/l3kn/org-fc/pull/137 I've made some changes to how card & scheduler data is passed because in the future I'd like to have the ability to pass data for multiple cards...

I believe the current state of #137 is solid enough to try on some new flashcards. One benefit here is that as long as the review history is logged correctly,...