From: Carsten Dominik <firstname.lastname@example.org>
To: Steven Haryanto <email@example.com>
Subject: Re: Perl parser, some questions
Date: Thu, 31 Mar 2011 10:39:51 +0200 [thread overview]
Message-ID: <61DB2A6C-1F7C-4CA6-972B-F30493D817E6@gmail.com> (raw)
On Mar 31, 2011, at 7:05 AM, Steven Haryanto wrote:
> 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?
This only applied to the #+STARTUP settings which can have a number
of keywords on a single line, like
#+STARTUP: align hidestars odd
> 2. For settings that can be applied near a block or table, like:
> #+TBLFM: @2$1=@1$1*2::@2$2=@1$2*3
> does it matter if it is specified before/after? Can there be separating lines between them? E.g.
Yes, there can be other lines in between, even though
this is probably not a good idea. The way the parser works
is that it runs through the buffer, finds CAPTURE etc and
applies it the next thing (table, link,...) that wants it.
> #+CAPTION: Some caption
> some text <-- allowed?
> #+LABEL: ...
> some more text <-- allowed?
> (And btw, multiple #+TBLFM below a table doesn't seem to work on my Emacs, all formulas need to be specified on a single (long) TBLFM setting.)
Yes, only one TBLFM line per table.
> 3. What constitutes a valid tag? Emacs doesn't seem to recognize tags (e.g. align them) if they contain a dash.
Tags are matched by [[:alnum:]_@#%:]+
Dashes are not allowed because this would be cumbersome for the
agenda tags matcher which uses "-" as NOT.
> 4. What is the difference between TYP_TODO/TODO/SEQ_TODO?
TODO and SEQ_TODO are the same. TYP_TODO is slightly different
in operation. When you press C-c C-t in a line with the keyword
defined by TYP_TODO, the task will immediately switch to DONE,
instead of to the next state in the sequence. I do believe the
manual explains this quite well, but I don't believe many people use this.
> (IIRC, the manual is not clear on this). Or between TAGS/FILETAGS.
TAGS defines tags that will be used in the buffer
and defines fast keyboard shortcuts for them. Though
you are allowed to also use tags that are not in tis list.
FILETAGS defines tags that are *inherited* by all trees in the buffer,
You can imagine FILETAGS as the tags specified on a level zero headline
of which all level one headlines in the buffer are children.
next prev parent reply other threads:[~2011-03-31 8:40 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
2011-03-31 8:39 ` Carsten Dominik [this message]
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).