org-pandoc-import VS emacs-which-key

You can try to use https://github.com/tecosaur/org-pandoc-import

Ooh, org-pandoc-imoort would be perfect for this! It'll convert your markdown files to org on import, provided you have pandoc installed, and then back when you save!

Orgmode's page about tools about import & export actually includes both to an entry about export to pandoc (ox-pandoc) as well as import from pandoc (org-pandoc-import).

It's always nice to see someone from the humanities interested in Emacs. I suspect that you'll find the best experience by using Org mode + Pandoc. This will let you write in a rather nice plaintext environment, and then export that to a .docx file. I don't think the styling will be great (could well be wrong though), but it should work fairly well :) Importing (from .docx to .org) is likely to be less smooth, but still decent.

The use case is: I maintain a little blog of my own and I use org mode for writing. I previously used Hakyll and Pandoc, but switched to Gatsby a while ago. Because Gatsby doesn't (didn't?) support using Pandoc in the pipeline, I switched to Orga, which provides a transformer for Gatsby. However, I've had a number of issues with Orga, so I'm looking for a replacement. I considered using org-pandoc-import and storing the documents as markdown instead, but I couldn't make it work properly. I'd also like to be able to utilize features such as (sequential) code block line numbering and links to code lines, which I haven't been able to find any support for outside of pure HTML export.

https://github.com/tecosaur/org-pandoc-import might help?

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?