emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer Stengele <rainer.stengele@online.de>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Lisp error when starting agenda
Date: Thu, 04 Jul 2013 21:07:35 +0200	[thread overview]
Message-ID: <51D5C7F7.6010106@online.de> (raw)
In-Reply-To: <87hagacqbg.fsf@bzg.ath.cx>

Am 04.07.2013 17:12, schrieb Bastien:
> Rainer Stengele <rainer.stengele@online.de> writes:
>
>> Lisp error is triggered by the SETUPFILE option:
>>
>> #+SETUPFILE: ~/org/GLOBAL_SETUP_DIPLAN.org
>>
>> If I remove that line everything works fine.
> Can you copy and past lines starting with "#+" from
> GLOBAL_SETUP_DIPLAN.org?
>
> Parsing those lines is where the error probably comes from,
> if that's so we need to fix it.
>
> Thanks again!
>

#+STARTUP:  overview
#+STARTUP:  hidestars inlineimages logdone nologrepeat nolognoteclock-out nologreschedule nologredeadline nologrefile
#+TAGS:     @DIPLAN @HOME(h) @IGN @KUNDE(k) @UNTERWEGS(U)
#+TAGS:     ADMIN(a) ASIEN(A) diplan(d) drill(D) EMAIL export(e) HIDE(H) HIDEAGENDA IGNORE(x) INFO(i) JWINTER(W)
LESEN(L) LPM(l) noexport(n) ONGOING(o)  PROJEKT REFILETARGET(r)
#+TAGS:     REVIEW_WEEKLY REVIEW_MONTHLY becom(b) fleckenm(f) foerster(F) rob(R) roth SERVICE stengele(s) TC(t)
TEL TDEIERL WARTEN(w) UBMED(u) ULLA(z)
#+SEQ_TODO: TODO NEXT WARTEN(w) HOLD(h) | MOVED DONE(d) CANCELED(c) DELEGATED
#+OPTIONS:   ^:{} \n:nil <:t todo:t toc:t
-*- coding:utf-8-unix; -*-

  reply	other threads:[~2013-07-04 19:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 13:35 Lisp error when starting agenda Rainer Stengele
2013-07-04 13:43 ` Rainer Stengele
2013-07-04 14:07 ` Bastien
2013-07-04 14:08   ` Rainer Stengele
2013-07-04 14:11     ` Bastien
2013-07-04 14:49       ` Rainer Stengele
2013-07-04 15:12         ` Bastien
2013-07-04 19:07           ` Rainer Stengele [this message]
2013-07-04 20:15             ` Bastien
2013-07-04 20:25               ` Rainer Stengele

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=51D5C7F7.6010106@online.de \
    --to=rainer.stengele@online.de \
    --cc=bzg@gnu.org \
    --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).