eli-qqB
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
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
Let’s say you have note text that’s open to change, and you still don’t want a headline.
I have thought of many ways to achieve this requirement, and one of them is similar to your solution: using explicit ID tags. My current approach is to use text properties and overlays. Every time I need to create a note, anki-helper will add the corresponding text properties and overlays to the original text (see the figure below). When I save the current file, anki-helper will also save the corresponding text properties. When I open this file again, anki-helper will add text properties and overlays to the string. This approach is still experimental, but I believe its advantage is that it does not modify the original text at all, while providing great flexibility.
In the following figure: “anki-card” at the end is an overlay indicating this paragraph is an anki note, and the whole paragraph has the three text properties, that lets me update/delete the note.
