emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: parsing options
Date: Tue, 16 Aug 2011 22:03:30 +0200	[thread overview]
Message-ID: <877h6di0od.fsf@gnu.org> (raw)
In-Reply-To: <87d3gue017.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 28 Jul 2011 11:24:20 -0700")

Hi Eric,

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Is there a generic function for parsing options lines at the top of a
> file? 

See `org-infile-export-plist'.

> I'd like to use some custom lines to set certain file-specific
> variables, and haven't quite figured out the best way to do that.
>
> It looks like org-set-regexps-and-options does that when you open a new
> file, but that's a bear of a function, and doesn't provide for setting
> your own options (or at least doesn't appear to, my eyes crossed while
> reading it).

`org-set-regexps-and-options' is used to set options keywords and
regexp, so depending on what you exactly want to do, you may have 
to add your own options keywords here...

> Is there any smaller function available for our own minor modes or use
> cases? Should I just use regexp search? If there isn't anything like
> this, would one be useful (something that either found an option value
> or returned a default, or found an alist of option values, or found an
> alist of values for options matching a regexp, etc)?

Mhh..  hard to help you more without knowing more precisely what you
want to achieve.  Perhaps an example would help.

Thanks!

-- 
 Bastien

next prev parent reply	other threads:[~2011-08-16 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 18:24 parsing options Eric Abrahamsen
2011-08-16 20:03 ` Bastien [this message]
2011-08-17  3:14   ` Eric Abrahamsen

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877h6di0od.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).