From: Eric S Fraga <firstname.lastname@example.org>
To: Steven Haryanto <email@example.com>
Subject: Re: Perl parser, some questions
Date: Thu, 31 Mar 2011 09:53:08 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <AANLkTinUhQoZ3D9JCexp+tkCvOjUhH=pWnJjaTvTmpvD@mail.gmail.com> (Steven Haryanto's message of "Thu, 31 Mar 2011 15:35:37 +0700")
Steven Haryanto <email@example.com> writes:
>From the manual (emphasis mine): "*Several setting words* can be in the same
> line, but you can also have multiple lines for the keyword." So I guess
> "setting words" mean setting's arguments (and not setting names, like
> specifying OPTIONS and TODO on the same line)?
Yes, I think the manual is trying to say that you can have
multiple #+OPTIONS: lines, say, each of which may have one or more
settings (tags:, t:, toc:, ...).
>> What is the main purpose of your parser?
> I first wrote it because I thought it would be fun, and CPAN does not have
> one already. The parser converts Org document into a tree of node objects,
> and can be a base for other efforts, like exporter to HTML/TXT/POD.
I asked because org has multiple uses, from outliner through to project
management, and it may help to concentrate on one particular aspect...
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 188.8.131.52
: using Org-mode version 7.5 (release_7.5.122.g2f72.dirty)
next prev parent reply other threads:[~2011-03-31 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 5:05 Perl parser, some questions Steven Haryanto
2011-03-31 8:21 ` Eric S Fraga
2011-03-31 8:35 ` Steven Haryanto
2011-03-31 8:53 ` Eric S Fraga [this message]
2011-03-31 8:39 ` Carsten Dominik
2011-03-31 9:15 ` Steven Haryanto
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 \
* 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).