emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Bastien <bzg@gnu.org>, org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Exploring properties
Date: Sun, 23 Feb 2020 08:40:11 -0500	[thread overview]
Message-ID: <CAJ51ETqo0qTOUmL8kZWs3JcXKo57Q-bPiNsvzMe2UDU_EJ9nQw@mail.gmail.com> (raw)
In-Reply-To: <20200223132024.whfg366o2dazcnim@rewasi>

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

org-ql (https://github.com/alphapapa/org-ql) is also quite good for this
kind of thing.

Here is even a database like query to find the heading, and EMAIL property
from all the files in a list returned by the function nb-org-files.

  :select '(cons (fifth (org-heading-components))
 (org-entry-get (point) "EMAIL"))
  :from (nb-org-files)
  :where '(and (property "EMAIL")))


Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213

On Sun, Feb 23, 2020 at 8:25 AM Vikas Rawal <vikasrawal@gmail.com> wrote:

> >
> > > I don't know if I have missed something obvious. But I am trying to
> > > read all the properties data (key-value pairs) into an R source code
> > > block (essentially to gather into a data.frame before further
> > > processing).
> >
> > You might want to look at `org-map-entries'.
> Thanks. It seems it will take more lisp than I can handle. But let me try.
> I think there is a potential to combine orgmode tags and properties, with
> a little more lisp may be, along with version control to create small
> database applications.
> It would be good to design something as a proof-of-concept.
> Vikas

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

  reply	other threads:[~2020-02-23 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23  3:42 Exploring properties Vikas Rawal
2020-02-23  9:35 ` Bastien
2020-02-23 13:20   ` Vikas Rawal
2020-02-23 13:40     ` John Kitchin [this message]
2020-02-23 13:21   ` Vikas Rawal
2020-02-23 13:40     ` Bastien
2020-02-24  4:12       ` Vikas Rawal
2020-02-24  8:39         ` Bastien
2020-02-25  2:58           ` Vikas Rawal
2020-02-25 13:35             ` John Kitchin

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:

  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=CAJ51ETqo0qTOUmL8kZWs3JcXKo57Q-bPiNsvzMe2UDU_EJ9nQw@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).