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

From: Michael Albinus <michael.albinus@gmx.de>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Local variables in org files
Date: Thu, 09 Jan 2014 21:51:36 +0100	[thread overview]
Message-ID: <87d2k0j2uf.fsf@gmx.de> (raw)
In-Reply-To: <87ob3luomu.fsf@alphaville.bos.redhat.com> (Nick Dokos's message of "Thu, 09 Jan 2014 11:05:29 -0500")

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?

--8<---------------cut here---------------start------------->8---
* COMMENT Local Variables

#+NAME: init
#+BEGIN_SRC elisp
(set (make-local-variable 'debbugs-org-ids) '(1 2 3))
#+END_SRC

#+CALL: init
--8<---------------cut here---------------end--------------->8---

However, I must have misread the documentation. The "#+CALL: init"
directive has no effect when loading a respective xxx.org file :-(

Best regards, Michael.

next prev parent reply	other threads:[~2014-01-09 20:52 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 [this message]
2014-01-09 21:39     ` Sebastien Vauban
2014-01-09 22:15       ` Michael Albinus
2014-01-09 22:29       ` Nick Dokos
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

  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=87d2k0j2uf.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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).