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 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.
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.
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?
This is used for traditional card format, where one headline is one card.
It’s all customizable, See card-that-are-not-entries and change-the-default-behavior
I see
anki-helper-requestlets 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.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.
https://preview.redd.it/ex8x388x0vvb1.png?width=681&format=png&auto=webp&s=8b46f4acb4f880141b4e164eab0509658b698dab
I am learning french, too. I my case, I use item list to collect words, for instance:
^(- [ ] Oui)
^(- [ ] Non)
^(- [ ] Peut-être.)
In this case, I can sync all words without recording the ID.