all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Local variables in org files
Date: Thu, 09 Jan 2014 17:29:01 -0500	[thread overview]
Message-ID: <87k3e8aixe.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 86iotsg7hd.fsf@somewhere.org

"Sebastien Vauban" <sva-news@mygooglest.com>
writes:

> Hello Michael,
>
> Michael Albinus wrote:
>> Nick Dokos <ndokos@gmail.com> writes:
>>
>>> Not sure if there are any limits for the top style but maybe you could
>>> combine the two styles of local variables - maybe:
>>>
>>> # -*- foo: (1 2 3 4) -*-
>>
>> This would move the problem to the headline. No idea, whether there is a
>> limit (to be tested). But this extremely long and ugly headline would be
>> visible - nothing I like to offer :-(
>>
>> But maybe we don't need the Local Variables block? Code blocks could help?
>>
>> * COMMENT Local Variables
>>
>> #+NAME: init
>> #+BEGIN_SRC elisp
>> (set (make-local-variable 'debbugs-org-ids) '(1 2 3))
>> #+END_SRC
>>
>> #+CALL: init
>>
>> However, I must have misread the documentation. The "#+CALL: init"
>> directive has no effect when loading a respective xxx.org file :-(
>
> Nope, it doesn't, but you can add an `eval' directive in your Local
> Variables section, and evaluate a call to the init block, like this:
>
> # Local variables:
> # eval: (sbe "init")
> # End:
>

Nice!

  parent reply	other threads:[~2014-01-09 22:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 15:21 Local variables in org files Michael Albinus
2014-01-09 16:05 ` Nick Dokos
2014-01-09 20:51   ` Michael Albinus
2014-01-09 21:39     ` Sebastien Vauban
2014-01-09 22:15       ` Michael Albinus
2014-01-09 22:29       ` Nick Dokos [this message]
2014-01-11  9:25         ` Bastien
2014-01-11 11:37           ` Sebastien Vauban
2014-01-12 11:43             ` Bastien
2014-01-11 15:31           ` Nick Dokos
2014-01-11 21:08             ` Sebastien Vauban
2014-01-10  6:23       ` Thomas S. Dye

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

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

  git send-email \
    --in-reply-to=87k3e8aixe.fsf@alphaville.bos.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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
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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.