From: Joost Kremers <joostkremers@fastmail.fm>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Programmatically handling org files
Date: Mon, 12 Sep 2016 23:59:05 +0200 [thread overview]
Message-ID: <87poo8dbkm.fsf@fastmail.fm> (raw)
In-Reply-To: <m21t0pdyc0.fsf@andrew.cmu.edu>
On Mon, Sep 12 2016, John Kitchin wrote:
>> I was wondering if there is some sort of (semi)official API for handling
>> org files programmatically. That's to say, is there a documented way for
>> non-org Emacs packages to manipulate (the contents of) org files?
>
> None that I know of. A non-elisp lib would have to be able to parse the
> org-files.
As you've already realised, I was asking about Elisp code that's not
part of or intended to extend orgmode.
>> Also, I was wondering if there's a way to hook into org-store-link. For
>> a particular major mode, I would like to be able to define what kind of
>> link is created when the user calls `org-store-link`. I looked at the
>> source of `org-store-link` and it looks like the answer is no, but I
>> thought I'd ask anyway. I could of course create the link myself and add
>> it to `org-stored-links` but that feels rather hackish and I suspect
>> will blow up in my face at some point in the future.
>
> You want to add a function to org-store-link-functions. The function
> should check if it is responsible for creating this link (for example by
> looking at the major mode). If not, it must exit and return nil. If yes,
> it should return a non-nil value after a calling `org-store-link-props'
> with a list of properties and values.
Great, thanks! I looked at the source of `org-store-link', but this
wasn't obvious to me. :-/
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2016-09-12 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 11:44 Programmatically handling org files Joost Kremers
2016-09-12 13:47 ` John Kitchin
2016-09-12 21:59 ` Joost Kremers [this message]
2016-09-12 18:21 ` Thorsten Jolitz
2016-09-12 18:30 ` John Kitchin
2016-09-12 21:37 ` Joost Kremers
2016-09-12 21:22 ` Joost Kremers
2016-09-12 22:10 ` Nick Dokos
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=87poo8dbkm.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).