emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nik Clayton <nik@ngo.org.uk>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: API for manipulating #+PROPERTY entries?
Date: Tue, 5 Mar 2019 13:38:47 -0500	[thread overview]
Message-ID: <CAJ51ETqfhu64TLPm6gFmNsPEU8_0A9KY6rzxPuLaeJ+VHg-izQ@mail.gmail.com> (raw)
In-Reply-To: <CAKJTzL5X3_yZ38Ns8M886FYfT4k4+wLxxLTYcgTBKQH7V3-JJA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

You might find a function like this one:
https://github.com/jkitchin/techela-emacs/blob/master/techela-grade.el#L149

helpful. There are some variations that do similar things.

John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



On Tue, Mar 5, 2019 at 1:51 AM Nik Clayton <nik@ngo.org.uk> wrote:

> Hoi,
>
> Is there an API for manipulating properties that are set in #+PROPERTY
> lines before the first headline of a file (i.e., not in a property drawer)?
>
> I've got some properties that (a) make sense when set for the whole file,
> and (b) the file contains multiple first level headings (which isn't going
> to change).
>
> Using org-entry-put when point is before the first headline throws a
> "Before first headline" error (when when the #+PROPERTY line already exists
> and I want to update an existing entry).
>
> N
>

[-- Attachment #2: Type: text/html, Size: 1831 bytes --]

      parent reply	other threads:[~2019-03-05 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  6:51 API for manipulating #+PROPERTY entries? Nik Clayton
2019-03-05  7:47 ` Nicolas Goaziou
2019-03-05 18:38 ` John Kitchin [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=CAJ51ETqfhu64TLPm6gFmNsPEU8_0A9KY6rzxPuLaeJ+VHg-izQ@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=nik@ngo.org.uk \
    /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).