From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: org-caldav-sync hangs
Date: Thu, 13 Aug 2020 11:00:34 +0200 [thread overview]
Message-ID: <87wo22539p.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: <87pn7ymwdo.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 10 Aug 2020 15:02:59 +0100")
Hi Eric,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Monday, 10 Aug 2020 at 14:47, Loris Bennett wrote:
>> The following used to work ca. 6-8 weeks ago to work and allow me to
>> synchronise events in an Org file with a calendar provided by a
>> Nextcloud instance:
>
> I had this problem in the past, or something similar. I found that I
> had to run org-lint on all my relevant files. Some of my files had the
> properties drawer in the wrong place (things have changed along the way
> with respect to where org expects these to be). Once I fixed them,
> everything has worked smoothly. I also use org-caldav-sync with a
> nextcloud instance.
>
> Just in case, and grasping at straws, another possibility may be that
> the file which keeps track of org IDs (~/.emacs.d/.org-id-locations on
> my system) has ended up inconsistent with your actual org files. You
> may be able to delete that file (make a copy in case I'm wrong) and it
> should be re-generated.
Thanks for the suggestions. Unfortunately all the relevant Org file
pass linting and regenerating .org-id-locations didn't help.
What I do occasionally see is this error:
up-list: Scan error: "Unbalanced parentheses", 388, 126
However I don't even know whether this is coming from Org or not, so I
can't tell whether it is relevant.
Cheers,
Loris
--
This signature is currently under construction.
next prev parent reply other threads:[~2020-08-13 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 12:47 org-caldav-sync hangs Loris Bennett
2020-08-10 14:02 ` Eric S Fraga
2020-08-13 9:00 ` Loris Bennett [this message]
2020-08-13 9:19 ` Robert Pluim
2020-08-13 10:35 ` Eric S Fraga
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=87wo22539p.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.de \
--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).