search

myuhe / org-gcal.el

Org sync with Google Calendar
449 stars 113 forks source link

Backtrace when syncing an item lacking a timestamp. #68

Open sje30 opened 8 years ago

sje30 commented 8 years ago

I get a backtrace when running org-gcal-sync on the following buffer (properties deleted)

* Test 1
  :PROPERTIES: ...
  :END:

  <2016-11-14 Mon>
* Test 2
  :PROPERTIES:
  :END:

  <2016-11-16 Wed>
* No diary here

In this section we have no diary.

Backtrace is at the end. Critically, must all of my entries in an org buffer have a timestamp? (I"m principally interested in syncing from org to gcal, where it cannot be assumed that each section has a timestamp.) Am I using the wrong tool?

Thanks, Stephen

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  org-gcal--archive-old-event()
  org-gcal-sync()
  funcall-interactively(org-gcal-sync)
  call-interactively(org-gcal-sync record nil)
  command-execute(org-gcal-sync record)
  execute-extended-command(nil "org-gcal-sync" nil)
  funcall-interactively(execute-extended-command nil "org-gcal-sync" nil)
  call-interactively(execute-extended-command nil nil)
  command-execute(execute-extended-command)
sje30 commented 8 years ago

aha. I just found this usage: https://github.com/myuhe/org-gcal.el/issues/16#issuecomment-40218161

which means I think that I've got the wrong tool.

telotortium commented 4 years ago

Hi everyone! This repository is obsolete - the actively developed fork is now https://github.com/kidd/org-gcal.el, which is also the "org-gcal.el" on MELPA (see #115). I'm one of the maintainers of https://github.com/kidd/org-gcal.el. I can't directly close issues or PRs on this repo, but please download https://github.com/kidd/org-gcal.el and see if your issue or PR is still applicable. If so, open an issue or PR on https://github.com/kidd/org-gcal.el. In any case, you should close your issue or PR in this repo.