Comment by dpbriggs

In practice I am not sure how true that is. There is a phenomenal ecosystem around org-mode that will require an amazing amount of work to recreate in other editors.

I haven't seem other editors get close to the convenience and integration org-mode has in emacs. For example, org-babel lets me dynamically generate entire sections of a README on github[0]:

    #+BEGIN_SRC python :results output raw :format org :exports results
    ... elided python to generate org mode ...
    #+END_SRC

Not to mention org-capture, org-agenda, or the various org-export-* functions. The deep hackiness of emacs lets this stuff just work naturally. And the quality of org-export is just amazing, especially when compared to say pandoc. I have done all of my university assignments in org-mode, augmenting with latex where required, and it just works. Same concept with my website, I have a tiny function to turn org-mode buffers into live html rendering experience with basic elisp:

    (defun make-blogging-mode ()
      (interactive)
      (toggle-word-wrap)
      (toggle-truncate-lines)
      (flycheck-mode)
      (flycheck-vale-toggle-enabled)
      (add-hook 'after-save-hook 'org-mode-export-hook)
      )

And a file hook (at the top of the org mode file so it runs automatically for me)

    # -*- find-file-hook: make-blogging-mode -*-

This isn't just a simple, context-free grammar that any other editor can emulate. It's an entire ecosystem that needs to be translated, and many have tried and failed.

Edit: Forgot to mention tables and the spreadsheet feature. Another hurdle a text editor will need to implement to recreate the experience

[0] https://github.com/dpbriggs/redis-oxide/blob/master/README.o...