Last time I tried using SRS I got annoyed having to edit my deck through the Anki interface. I want to live in Vim when I edit large quantities of texty stuff, not poke through a GUI that’s different for every application.
So what options have I got? Googling attempts get me people trying to learn Vim with SRS, not people doing SRS with Vim. Anki has a text export and I could probably rig it up to an export-edit-import cycle without that much fuss. But the text export doesn’t carry repetition data, and I worry about that being lost in the process. Though Anki did seem to be able to update the deck with an import of an exported and edited file instead of just remaking everything from scratch.
Emacs has org-drill, but it feels sorta kludgy and it’s Emacs-only.
Rolling my own might be an option, I can just crib the algorithm from somewhere and the rest of the application logic isn’t terribly complicated. I’m envisioning something like a text file for the deck where the cards are set up using some sort of lightweight markup, and repetition data is stored in base64 blobs on special lines and updated by the SRS app when it operates on the file. Could also have the app maintain a separate database with hashes of card contents as keys (this would zap a card from the db whenever it’s edited, but then again you might often want to refresh things after an edit) and keep the actual card text file immutable.
Displaying LaTeX or images would be tricky if I wanted to be old-school and run this on command line. Could also make a web app run the thing.
When I use Anki, all I’m doing is pressing buttons (I don’t have it make me type in answers; I have no urge whatsoever to lie to it about whether I got the right answer) so I don’t miss not having Vim.
When I make any more than four or six new cards at a time, I do it in Vim or write a program to do it. Anki can import CSV files.
Last time I tried using SRS I got annoyed having to edit my deck through the Anki interface. I want to live in Vim when I edit large quantities of texty stuff, not poke through a GUI that’s different for every application.
So what options have I got? Googling attempts get me people trying to learn Vim with SRS, not people doing SRS with Vim. Anki has a text export and I could probably rig it up to an export-edit-import cycle without that much fuss. But the text export doesn’t carry repetition data, and I worry about that being lost in the process. Though Anki did seem to be able to update the deck with an import of an exported and edited file instead of just remaking everything from scratch.
Emacs has org-drill, but it feels sorta kludgy and it’s Emacs-only.
Rolling my own might be an option, I can just crib the algorithm from somewhere and the rest of the application logic isn’t terribly complicated. I’m envisioning something like a text file for the deck where the cards are set up using some sort of lightweight markup, and repetition data is stored in base64 blobs on special lines and updated by the SRS app when it operates on the file. Could also have the app maintain a separate database with hashes of card contents as keys (this would zap a card from the db whenever it’s edited, but then again you might often want to refresh things after an edit) and keep the actual card text file immutable.
Displaying LaTeX or images would be tricky if I wanted to be old-school and run this on command line. Could also make a web app run the thing.
When I use Anki, all I’m doing is pressing buttons (I don’t have it make me type in answers; I have no urge whatsoever to lie to it about whether I got the right answer) so I don’t miss not having Vim.
When I make any more than four or six new cards at a time, I do it in Vim or write a program to do it. Anki can import CSV files.
Yeah, on further thought making and reviewing the cards are disparate enough activities that the import workflow should work fine.