Neat!
Hi, I found that we have the same idea. I recently wrote a similar package that
focuses on customizability and not modifying the original text. My idea is that
we should allow users to define which parts are the front side of the card,
which parts are the back side, which parts need to create an ID, and so on, so
my package focuses more on customizability. Additionally, I found that we both use org
emphases as the marker for cloze, which is really coincidental :) .
Here is my package: https://github.com/Elilif/emacs-anki-helper
You beautiful bastard. Starred.
Yes, org emphasis makes it easy with the regexp org-emph-re :-)
From your source code, I infer that the note ID is saved in a property ANKI_NOTE_ID, which always goes in a property drawer, correct? Or did you find a way to skip recording the ID in some cases? Or detach property drawers from headlines?
I infer that the note ID is saved in a property ANKI_NOTE_ID, which always goes in a property drawer, correct?
This is used for traditional card format, where one headline is one card.
Or did you find a way to skip recording the ID in some cases? Or detach property drawers from headlines?
It’s all customizable, See card-that-are-not-entries and change-the-default-behavior
I see anki-helper-request lets the user make their own AnkiConnect request, so I see it’s totally customizable (for programmers). Which is a good idea, but I’m also interested in automating some default syntaxes. I’m curious how you personally would do it? Let’s say you have note text that’s open to change, and you still don’t want a headline.
