Hi Jenia,
Sounds cool. I hope you choose to get involved in the Org-community!
jenia.iv...@gmail.com (jenia.ivlev) writes:
> I was to learn emacs lisp and I figured one of the ways to do it is to
> read someone else's commit.
> Can you please tell me what feature is your branch implementing?
Sorry, it was just a local branch and the merge message is an error. See
the thread containing something like [git-101].
It's patch d135f1a37f00179fcc711b769cebc0f34d34172d and
17cbd90e5d21948e0f2e3f1d0b0a3def64db36f8 which makes #+INCLUDE support
footnotes better and make the level of #+INCLUDE not nest.
* Some more general advice follows, which is probably not news to you.
IMO, the state-of-the-art in Org is org-element.el which is an interpreter
of the Org-syntax and ox.el, which is the export framework utilizing
org-element.el. Try to do
M-: (org-element-at-point) RET
at various places in your Org-buffer, and you will see the lisp
representation of the element.
Org-element enables very rapid hacking; from the export framework, to
hacks in your init (e.g. I type space twice to leave math-subscribes and
automatically export UPPERCASE using smallcaps).
* How to get started
I sure there's still "old" functions that can be rewritten using
org-element.el. So if there's something you know well, e.g. as a user,
that might be a great place to get started!
Another way to get to read some code to would be add docstring for some of
the functions lacking a docstring in org-macs.el.
Org-folks are generally generous in reviewing patches and the tone is
friendly.
Cheers,
Rasmus
--
El Rey ha muerto. ¡Larga vida al Rey!
