-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editing cards in Emacs #4
Comments
Simple editing is possible (Update existing cards' content), but complicated editing is probably not in |
Finally, I plan to work on Adding/Updating/Deleting on Anki Database directly, this needs some work and a lot of tests. |
You are probably aware of anki-editor. Perhaps it may be of use or could be combined with this project? Is there an argument to not rely on the Anki application database (or on Anki at all) but instead create your own. I really like Anki but I always have this (perhaps unfounded) fear that my large database gets corrupted and I lose access to my cards and the work I put into creating them. That's why solutions within Emacs appeal to me and to be able to create the cards as plaintext as I don't have to fear them getting corrupted. The one drawback I see with plaintext cards is that the file would get large pretty quickly if one adheres to the recommendation to keep everything in a single deck (one file) rather than splitting the information into multiple decks (separate files). |
Yes. It is possible, now anki.el has ability to read the Anki database but not write. I can provide an import function for it. Maybe in pure org format compatable with Anki Editor. But about the card edit feature, I still can not find a good way to implement. Maybe combine with anki editor and pure org format is a great option. Importing Anki database as org formats is easy and seems more flexible and promising. I will implement it. |
Is it possible to edit the
shrface
rendered card in its Emacs buffer and have the results write back to the Anki database?The text was updated successfully, but these errors were encountered: