From: Steven Haryanto <email@example.com>
To: Steven Haryanto <firstname.lastname@example.org>, email@example.com
Subject: Re: Perl parser, some questions
Date: Thu, 31 Mar 2011 15:35:37 +0700 [thread overview]
Message-ID: <AANLkTinUhQoZ3D9JCexp+tkCvOjUhH=pWnJjaTvTmpvD@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On Thu, Mar 31, 2011 at 3:21 PM, Eric S Fraga <firstname.lastname@example.org> wrote:
> Steven Haryanto <email@example.com> writes:
> > Hi all,
> > I'm writing an Org parser for Perl. There are a few things about the
> > syntax which are still unclear to me.
> > 1. The manual says that multiple (different) in-buffer settings can be
> > specified on the same line, but so far I haven't found such example
> > anywhere. What is the syntax for this?
> If you are referring to lines like this one:
> #+OPTIONS: oddeven hideblocks
> the syntax is space separated options.
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)?
> 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.
[-- Attachment #2: Type: text/html, Size: 1735 bytes --]
next prev parent reply other threads:[~2011-03-31 8:35 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 [this message]
2011-03-31 8:53 ` Eric S Fraga
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).