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:21:07 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <AANLkTimsAQ7FnOkm-oFb1VAUrE5KjoG6LKGbH_h1J3pq@mail.gmail.com> (Steven Haryanto's message of "Thu, 31 Mar 2011 12:05:53 +0700")
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.
I cannot really help you with the rest of your questions unfortunately.
I do think you may end up getting a little frustrated in the near
future: org has grown "organically" and so doesn't have a well defined
or consistent syntax across all the features. This is not a criticism
of org mode, by the way... just an observation!
The only real definition of the syntax is the (ever changing) emacs lisp
code that implements it.
What is the main purpose of your parser?
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 126.96.36.199
: using Org-mode version 7.5 (release_7.5.122.g2f72.dirty)
next prev parent reply other threads:[~2011-03-31 8:21 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 [this message]
2011-03-31 8:35 ` Steven Haryanto
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).