anki-editor VS emacs-which-key

Also, I sometimes use flashcards, they really help me to remember the material. I am creating flashcards using a package called anki-edior. My flashcards are my notes. I don't need to go somewhere else to search through my flashcards.

If you are interested in the spaced-repetition learning approach, you can try org-drill and you will use Emacs for notes production and repetition; if, like me, you prefer integrating your workflow with Anki, there's anki-editor, "a minor mode for making Anki cards with Org": the repo here. This way, you will create notes in Emacs but the repetition will be done in Anki (which means you can use Ankidroid on your phone for studying what you wrote in Emacs)

I do however create all my decks in Emacs' Org mode using louietan/anki-editor and export to Anki via the plugin FooSoft/anki-connect. This way I never worry about my decks getting corrupted. I actually just have one large deck but anki-editor allows me to separate my deck into separate org files which is convenient.

Sure. I write my cards in Emacs' Org mode and specifically the louietan/anki-editor minor mode. Org mode is a markup file format like markdown (but superior IMHO as it is more intuitive). With anki-editor I can export my plaintext cards to HTML by Org-mode’s HTML export backend (it has many others) with specific markers (e.g. latex) translated to Anki style. I do this with Anki open and the Anki-Connect plugin installed. It is this plugin that allows the anki-editor to push the cards to Anki. Within Anki I use the provided sync function to sync my cards with my phone. I only ever edit the cards via Emacs as anki-editor only pushes to Anki it does not pull from it.

A blog post would be much more useful for this kind of thing. Here's a similar post using anki-editor:

I write my cards in plaintext (Emacs Org mode via anki-editor) and push them to Anki via anki-connect. The advantages for me are:

create Anki cards with Emac's anki-editor and push them to Anki with anki-connect. There is also a markdown equivalent of anki-editor if you prefer that format plus packages to perform your SRS within Emacs itself such as org-drill, org-fc and pamparam.

Here's my use case: I'm maintaining Anki notes in my Org files using the anki-editor package. Every few hours during the day, I like to sync my Anki notes from Emacs to Anki using the following code:

For learning: I put the ones I can't "just" remember into Anki, a FOSS flashcard system based on spaced repetition (for example, the front of a card would be "emacs org: how do you toggle a checkbox?", and the back would be "C-c C-x C-b"). I use anki-editor-mode to make this faster. Then I do an Anki review every day.

Anki-editor https://github.com/louietan/anki-editor

I think which-key already solves exactly that: https://github.com/justbur/emacs-which-key

As for the "complicated keybindings general" -- I assume because remembering things like C-x C-s is hard because of the shifted keystrokes? I get that, and there is in fact a solution for less used keybindings which I love, called 'which-key' https://github.com/justbur/emacs-which-key

I would recommend installing the which-key package, which is a fantastic discoverability aid. If you ever want an example config to get some inspiration, I have one here: Emacs Bedrock

Make sure you have which-key installed and turned on. When using a keybinding that has a prefix (like C-x or C-c), it displays all the keybindings that start with that prefix.

which-key for the shortcut menus

there are some packages to help with the keybings, which-key shows a list of keybind and its command and (guru-mode)[https://github.com/bbatsov/guru-mode] enforces to use the "best" keybind, for exemple, it forces you to use C-n to move the cursor, blocking you to use the down key, and if you press the down key, it show a text in minibuffer to the best keybind.

Thanks for confirming, I think it's an issue in which-key itself: https://github.com/justbur/emacs-which-key/pull/166

If you haven't already, definitely check out the package which-key.

> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.

CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:

A couple of nice examples of discoverability in keyboard-focused programs:

- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.

- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.

[0] https://github.com/justbur/emacs-which-key

[1] https://github.com/liuchengxu/vim-which-key

[2] https://magit.vc/

[3] https://emacsair.me/2017/09/01/magit-walk-through/

Am I right in thinking this is quite similar to which-key?