Error with org-gcal-post-at-point : Wrong type argument: number-or-marker-p, nil

[juan-bolivar]

Hello @kidd ,

First of all , great package , it's a godsend!!! , thanks also @myuhe

keep up the good work!

Can you please help me or give me some light on where to look for a solution.

I'm getting the following error when trying the function org-gcal-post-at-point

error in process sentinel: Wrong type argument: number-or-marker-p, nil [2 times]

The following is the file i'm trying to sync:

* Cumple Christiam
  :PROPERTIES:
  :END:
  <2018-08-05 dom.>

and this is my config file:

(setq package-check-signature nil)
(require 'org-gcal)
 :ensure t
 :config
(setq org-gcal-client-id "#Private.apps.googleusercontent.com"
	org-gcal-client-secret "#Private"
	org-gcal-file-alist '(("#Private@gmail.com" .  "D://Documents//org-mode//gcal.org")))

(add-hook 'org-agenda-mode-hook (lambda () (org-gcal-sync) ))
(add-hook 'org-capture-after-finalize-hook (lambda () (org-gcal-sync) ))
(add-hook 'post-command-hook 'cw/org-auto-toggle-fragment-display t )

I'm using emacs in a Windows10 Machine

Muchas Gracias de Antemano!

[telotortium]

@juan-bolivar Try setting these variables

(setq toggle-on-error t)
(setq deferred:debug-on-signal t)

and then run org-gcal-post-at-point again. Does the debugger pop up? If so, copy and paste the backtrace here.

[juan-bolivar]

thanks @telotortium for the quick response ,

Debugger , doesn't show up.

I'm getting the same error in the mini-buffer :

error in process sentinel: Wrong type argument: number-or-marker-p, nil [2 times]

does this function require the cursor to be at the start of the file?

[shankar2k]

Has any progress been made on this issue? I have the same problem as others. The backtrace is:

Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
  request--curl-callback(#<process request curl> "finished\n")

This issue appears to be related to the changes made in request.el #28

[seblemaguer]

Hello,

it seems on my side that the fact that the date is not in a "scheduled" property is causing this problem.

[telotortium]

Yes, right now the date can be in one of two locations: - SCHEDULED property - At the top of the :org-gcal: drawer. I should probably document this better...

…

On Mon, Aug 26, 2019 at 3:42 AM Sébastien Le Maguer < ***@***.***> wrote: Hello, it seems on my side that the fact that the date is not in a "scheduled" property is causing this problem. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AANMVDIRHMDVCUKB3C2NOPLQGOXR3A5CNFSM4FMSGPXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EABOI#issuecomment-524812473>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANMVDM67P7CO4VTPV3ROHDQGOXR3ANCNFSM4FMSGPXA> .

-- Robert Irelan rirelan@gmail.com