From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Haryanto Subject: Re: Perl parser, some questions Date: Thu, 31 Mar 2011 15:35:37 +0700 Message-ID: References: <87tyejr98s.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf302d4bfe7b8564049fc32d32 Return-path: Received: from [140.186.70.92] (port=50471 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5DLy-00032p-Ko for emacs-orgmode@gnu.org; Thu, 31 Mar 2011 04:35:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q5DLu-0000U2-2F for emacs-orgmode@gnu.org; Thu, 31 Mar 2011 04:35:39 -0400 Received: from mail-yw0-f41.google.com ([209.85.213.41]:37203) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q5DLt-0000Tw-Uf for emacs-orgmode@gnu.org; Thu, 31 Mar 2011 04:35:38 -0400 Received: by yws5 with SMTP id 5so1045864yws.0 for ; Thu, 31 Mar 2011 01:35:37 -0700 (PDT) In-Reply-To: <87tyejr98s.fsf@ucl.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Steven Haryanto , emacs-orgmode@gnu.org --20cf302d4bfe7b8564049fc32d32 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Mar 31, 2011 at 3:21 PM, Eric S Fraga wrote: > Steven Haryanto writes: > > > Hi all, > > > > I'm writing an Org parser for Perl[1]. 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. -- sh --20cf302d4bfe7b8564049fc32d32 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Mar 31, 2011 at 3:21 PM, Eric S Fraga <e.fraga@ucl.ac.uk<= /a>> wrote:
Steven Haryanto <stevenharyanto@gmail.com> writes:

> Hi all,
>
> I'm writing an Org parser for Perl[1]. There are a few things abou= t 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 exampl= e
> 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 th= e same line, but you can also have multiple lines for the keyword." So= I guess "setting words" mean setting's arguments (and not se= tting names, like specifying OPTIONS and TODO on the same line)?
=A0
What is the main purpose of y= our parser?

I first wrote it because I = thought it would be fun, and CPAN does not have one already. The parser con= verts Org document into a tree of node objects, and can be a base for other= efforts, like exporter to HTML/TXT/POD.

--
sh
--20cf302d4bfe7b8564049fc32d32--