From: Mark Elston <m_elston@comcast.net>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [OT] Taskwarrior, nice GTD-oriented CLI thing
Date: Fri, 04 Feb 2011 13:53:51 -0800 [thread overview]
Message-ID: <4D4C756F.2010303@comcast.net> (raw)
In-Reply-To: <871v3n34n0.fsf@gmail.com>
On 2/4/2011 11:16 AM, Eric Schulte wrote:
> Mark Elston<m_elston@comcast.net> writes:
>
>> On 2/3/2011 8:03 PM, Torsten Wagner wrote:
>>> Hi Marcelo,
>>>
>>> Emacs can run as a dameon and as that you could access it via
>>> emacsclient. What is needed is a nice interface to allow to send simple
>>> requests to insert and fetch data from org-mode. Some of the org-mode
>>> function might do this already, however, I guess a decent layer which
>>> hides the complex org-mode routines and provides simple to use in- and
>>> output functions might be more effective.
>>>
>>
>> There is also PyOrgMode which can probably be developed as an
>> intermediary between the two. I, for one, find Python *much* more
>> approachable than elisp... :)
>>
>
> The only problem here is that you will invariably begin re-implementing
> the entirety of Org-mode in python. I think that an emacsclient backend
> exposing an Org-mode api is the best bet, then a Python wrapper around
> such a backend could be appropriate for writing the front-end interface.
>
I suppose that depends on what the CLI would have to do. This
discussion was about how to transfer data between the two frameworks.
You wouldn't have to implement all of org-mode in python to read through
an org-mode file, though I admit some sections would be more difficult
than others (org-babel stuff, for example).
I have found that the kind of stuff I would like to transfer from org to
something else (and vice versa) is pretty simple most of the time. The
more complex org-files are not calendar/agenda kinds of things but
documents I use org to manage as I write (class notes/handouts/etc). My
calendar/agenda stuff is reasonably simple and could pretty easily be
parsed by most languages that have some support for parsing (built-in,
or library/tool support a la yacc/lex, etc.). Other people might have
more significant requirements, I suppose.
Mark
next prev parent reply other threads:[~2011-02-04 21:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 4:34 [OT] Taskwarrior, nice GTD-oriented CLI thing Marcelo de Moraes Serpa
2011-02-03 12:41 ` Eric S Fraga
2011-02-03 18:29 ` Marcelo de Moraes Serpa
2011-02-03 18:32 ` Marcelo de Moraes Serpa
2011-02-03 19:11 ` Erik Iverson
2011-02-03 21:01 ` Eric S Fraga
2011-02-03 21:05 ` Erik Iverson
2011-02-03 22:04 ` Marcelo de Moraes Serpa
2011-02-11 11:14 ` Bastien
2011-02-11 19:48 ` Marcelo de Moraes Serpa
2011-02-04 1:14 ` Torsten Wagner
2011-02-04 2:59 ` John Hendy
2011-02-04 3:12 ` Torsten Wagner
2011-02-04 3:51 ` Marcelo de Moraes Serpa
2011-02-04 4:03 ` Torsten Wagner
2011-02-04 4:23 ` Mark Elston
2011-02-04 19:16 ` Eric Schulte
2011-02-04 21:53 ` Mark Elston [this message]
2011-02-04 16:22 ` Christopher Allan Webber
2011-02-04 18:03 ` Marcelo de Moraes Serpa
2011-02-07 15:45 ` Christopher Allan Webber
2011-02-04 15:48 ` Matt Lundin
2011-02-04 9:19 ` Eric S Fraga
2011-02-05 9:25 ` Dirk-Jan C. Binnema
2011-02-05 20:52 ` Eric S Fraga
2011-02-06 17:50 ` Dirk-Jan C. Binnema
2011-02-06 19:14 ` Eric S Fraga
2011-02-06 17:52 ` Dirk-Jan C. Binnema
2011-02-04 2:59 ` Marcelo de Moraes Serpa
2011-02-04 4:00 ` Torsten Wagner
2011-02-04 20:38 ` Eric Schulte
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=4D4C756F.2010303@comcast.net \
--to=m_elston@comcast.net \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/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).