emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: giles@pexip.com
Cc: emacs-orgmode@gnu.org
Subject: Re: org-caldav issue: Search failed: ";\\([A-Za-z0-9-]+\\)="
Date: Wed, 30 Jan 2013 22:26:09 +0100	[thread overview]
Message-ID: <87libamkge.fsf@engster.org> (raw)
In-Reply-To: <m27gmu4gsm.fsf@jujutsu.org.uk> (giles@pexip.com's message of "Wed, 30 Jan 2013 19:22:33 +0000")

'giles' writes:
> David Engster <deng@randomsample.de> writes:
>> Could you please do M-x toggle-debug-on-error before running the sync
>> and post the resulting backtrace here?
>
> Slightly different behaviour this time: first seven events synced fine,
> number 8 blew up the same way.
>
> Debugger entered--Lisp error: (search-failed ";\\([A-Za-z0-9-]+\\)=")
>   re-search-forward(";\\([A-Za-z0-9-]+\\)=" nil nil)
>   icalendar--read-element(VEVENT nil)
>   icalendar--read-element(VCALENDAR nil)
>   icalendar--read-element(nil nil)

There must be something weird with the events you have. Could be that
it's the special characters you mentioned, but I'm afraid I'll need to
see the event which triggers this.

I just pushed a change to org-caldav which introduces the option for
excessive debug output. Please pull the new version and do

(setq org-caldav-debug-level 2)

before running org-caldav-sync. The iCalendar events will then be put
fully into the *org-caldav-debug-buffer*. Please send me the event which
triggers this bug; it should simply be the last one you see in there.
You can also send me the whole buffer, of course, but *please* remember
to edit/delete any private data from these events you don't want me to
see. I'd also recommend to send it directly to me and not to the list.

-David

  reply	other threads:[~2013-01-30 21:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 15:30 org-caldav issue: Search failed: ";\\([A-Za-z0-9-]+\\)=" giles
2013-01-30 16:01 ` David Engster
2013-01-30 19:22   ` giles
2013-01-30 21:26     ` David Engster [this message]
2013-02-02 15:57       ` David Engster
2013-02-04 20:04         ` giles
2013-01-30 19:30   ` giles

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=87libamkge.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=giles@pexip.com \
    /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).