debanjandhar12 / logseq-anki-sync

An logseq to anki syncing plugin with superpowers - image occlusion, card direction, incremental cards, and a lot more.
GNU Affero General Public License v3.0
465 stars 34 forks source link

Hide Logseq cloze syntax in Anki for parent bullet points #271

Closed CappieXL closed 6 months ago

CappieXL commented 6 months ago

Describe the solution you'd like Whenever I have a cloze in Logseq which is also the parent to extra cards, then when I review those children cards the cloze syntax in logseq still shows. See Image for example. The issue is that the line:"Wet 1: {{c1 Vul je emmers in de juiste volgorde}}" shows "{{c1" and "}}". image

Describe how it will help your workflow If those could automatically be removed when syncing to anki, it would make cards less cluttered and would allow me to be as hierarchical as I want with my information in Logseq.

Describe alternatives you've considered I tried fixing this with CSS. That's seems to not be possible. Editing the html/javascript is not stable as those get overwritten every time you sync logseq to anki.

Will try to build it myself over the weekend if I find the time and create a branch. Seems like a fun way to contribute.

CappieXL commented 6 months ago

Decided to fix this by rearranging the information structure in which I capture the book in Logseq.

Rather than having:

- topic
    - category
       - question about category #card
          - answer
       - subcategory 1: {{c1 foo}}
       - subcategory 2: {{c1 bar}}
       - etc.

I decided to rearrange to:

- topic
   - category #card #incremental
      - subcategory 1: foo
      - subcategory 2: bar
   - question about category #card
      - answer

Because: 1) it was easier than changing code 2) the reason I wanted to do "subcategory 1: {{c1 foo}}" in the first place was for the hint "subcategory x:". Knowing the question was, which subcategory was the x-th. However, since it's sandwiched between x-1 and x+1, that clue is already given. I think this holds true generally for this use case.