emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christoph LANGE <math.semantic.web@gmail.com>
To: Org mode <emacs-orgmode@gnu.org>
Subject: org-contacts-anniversaries 'Bad sexp' bug keeps haunting me
Date: Mon, 29 Sep 2014 11:50:29 +0200	[thread overview]
Message-ID: <54292B65.9020605@gmail.com> (raw)

Hi all,

for a while I had been able to run org-contacts-anniversaries with 
BIRTHDAY dates successfully, as explained at the bottom of 
https://julien.danjou.info/projects/emacs-packages#org-contacts.  This 
was on 64-bit Linux.  On 32-bit Windows I had the function disabled, as 
I have contacts both before 1970.  (See this thread: 
http://comments.gmane.org/gmane.emacs.orgmode/42139)

Now, for the first time, I'm running a 64-bit Emacs on Windows 
(http://emacsbinw64.sourceforge.net/).  I was confident that 
org-contacts-anniversaries would work for me, but it didn't.  Once more 
any invocation of an agenda involving org-contacts-anniversaries haunted 
me with the "Bad sexp" error message, pointing to the line in my 
contacts.org that contains "%%(org-contacts-anniversaries)".

I am running org-8.2.7c from ELPA, on Emacs 24.4.50.1.

I think I didn't make any of the mistakes documented previously:

* running a mixed Org installation (Org as bundled with Emacs, plus 
non-bundled packages; http://stackoverflow.com/a/15568713/2397768)

* using the wrong syntax for org-contacts-files 
(http://stackoverflow.com/a/14057170/2397768)

* using empty BIRTHDAY fields (http://stackoverflow.com/a/21968778/2397768)

* not having diary loaded 
(https://www.mail-archive.com/emacs-orgmode@gnu.org/msg48710.html – but 
isn't it actually loaded automatically by org-agenda.el when 
org-agenda-include-diary is set to t?)

FYI this is how I disabled org-contacts-anniversaries on non-64-bit 
systems:

; disable anniversaries on non-64-bit systems (as they don't handle 
dates before 1970)
(defadvice org-contacts-anniversaries (around 
disable-org-contacts-anniversaries-on-32-bit)
   "No anniversaries on 32-bit systems"
   (if (string-prefix-p "x86_64" system-configuration)
       (ad-do-it)))
(ad-activate 'org-contacts-anniversaries)

This code does not cause my problem.  I have tested it before, and 
without this code I'm still getting the "Bad sexp".

I'm giving up for now, reverting to manually maintained entries like 
this in my contacts.org:

%%(org-anniversary YYYY MM DD) Name (%d years)

Cheers, and thanks in advance for any helpful advice,

Christoph

-- 
Christoph Lange, Enterprise Information Systems Department
Applied Computer Science @ University of Bonn; Fraunhofer IAIS
http://langec.wordpress.com/about, Skype duke4701

→ SEMANTiCS conference: Transfer–Engineering–Community.
   Leipzig, Germany, 4–5 September (workshops 1–3 September).
   Including Vocabulary Carnival, LOD for SMEs, Linked Data Quality.

                 reply	other threads:[~2014-09-29  9:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54292B65.9020605@gmail.com \
    --to=math.semantic.web@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).