From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: how to debug Archive view in custom agenda Date: Fri, 11 Apr 2014 13:04:47 -0400 Message-ID: <87bnw7bxw0.fsf@alphaville.bos.redhat.com> References: <87fvljbznw.fsf@alphaville.bos.redhat.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34686) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WYet3-0007AE-0m for emacs-orgmode@gnu.org; Fri, 11 Apr 2014 13:05:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WYesu-0006J5-Sl for emacs-orgmode@gnu.org; Fri, 11 Apr 2014 13:05:08 -0400 Received: from plane.gmane.org ([80.91.229.3]:47895) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WYesu-0006Iu-Lh for emacs-orgmode@gnu.org; Fri, 11 Apr 2014 13:05:00 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WYest-0000Jy-3Y for emacs-orgmode@gnu.org; Fri, 11 Apr 2014 19:04:59 +0200 Received: from nat-pool-bos-t.redhat.com ([66.187.233.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Apr 2014 19:04:59 +0200 Received: from ndokos by nat-pool-bos-t.redhat.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Apr 2014 19:04:59 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Ken Mankoff writes: > On 2014-04-11 at 18:26, Nick Dokos wrote: >> Ken Mankoff writes: >> >>> when I try to view the Archive (v A) in my custom agenda view, I get an >>> error: >>> >>> Rebuilding agenda buffer... >>> org-refresh-properties: Wrong type argument: integer-or-marker-p, nil >>> >>> When I view Archive in the timeline for a single Org file (C-c a L v A) >>> it works just fine. >>> >>> How do I debug the above message to determine what might be the cause of >>> the error? >>> >> >> (setq debug-on-error t) >> >> try the v A again and send in the backtrace. >> > > I can send the backtrace if you want, but I figure it out. I had an " > :Effort: :15" in an archive file which was causing the problem. Not sure > why. Perhaps it needed to be 00:15? Anyway, I just removed it and it > works again. > Did you figure it out with the help of the backtrace? Send it anyway: it can't hurt and it might help somebody.