From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Hi Rasmus. What does you branch do?
Date: Thu, 25 Dec 2014 10:55:38 +0100 [thread overview]
Message-ID: <87h9wkyrxh.fsf@gmx.us> (raw)
In-Reply-To: 87vbl0i60f.fsf@gmail.com
Hi Jenia,
Sounds cool. I hope you choose to get involved in the Org-community!
jenia.ivlev@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!
prev parent reply other threads:[~2014-12-25 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 6:43 Hi Rasmus. What does you branch do? jenia.ivlev
2014-12-25 9:55 ` Rasmus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9wkyrxh.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).