emacs-orgmode@gnu.org archives
 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 11:05:29 -0500	[thread overview]
Message-ID: <87ob3luomu.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 87a9f5xjsv.fsf@gmx.de

Michael Albinus <michael.albinus@gmx.de> writes:

> Hi,
>
> I'm trying to save the result of "M-x debbugs-org" into a file (this is
> a TODO list). For further handling, also some buffer local variables
> must survive. Therefore, I append at the very end of that file something
> like this:
>
> * Local Variables
> ** Local Variables:
> ** eval: (debbugs-org-mode 1)
> ** debbugs-org-ids: (1 2 3)
> ** End:
>
> This has the nice effect, that those variables do not disturb in
> overview mode, because they look like
>
> * Local Variables...
>
> Being invisible would be even better, but so what.
>
> Unfortunately, the value of debbugs-org-ids could be very loooong,
> exceeding the 3000 chars limit the "Local Variables:" section size is
> allowed to be in Emacs. So I must rearrange things like this:
>
> * Local Variables
> ** debbugs-org-ids: (1 2 3)
> ** Local Variables:
> ** eval: (debbugs-org-mode 1)
> ** debbugs-org-ids: (access-the-value-above)
> ** End:
>
> Is there some functionality in org I could use implementing
> `access-the-value-above'? It is org structure, so I'm hoping there is an
> easy way to access a given node with a well defined position.
>
> Or maybe there is already a clever way storing local variables in an org
> file, which I'm not aware of.
>
> Thanks, and best regards, Michael.

Not sure if there are any limits for the top style but maybe you could
combine the two styles of local variables - maybe:

--8<---------------cut here---------------start------------->8---
# -*- foo: (1 2 3 4) -*-
* foo

#+BEGIN_SRC elisp
debbugs-org-ids
#+END_SRC

#+RESULTS:
| 1 | 2 | 3 | 4 |

* COMMENT Local variables

** Local Variables:
** eval: (setq debbugs-org-ids foo)
** End:
--8<---------------cut here---------------end--------------->8---

Nick

  reply	other threads:[~2014-01-09 16:05 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 [this message]
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
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=87ob3luomu.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 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).