Re: Fwd: errors when using org-agenda

[William McCoy <wdm8588@gmail.com>]

Ok, great -- that fixed it!  I thought I had been careful to get rid of 
my old org from org elpa before I installed 9.5.  However, I hadn't 
considered that there was an older org still installed that had been 
packaged with my emacs 27.2 installation.

So thanks very much for your quick advice.  It's very nice to have that 
functionality back.


Bill


On 10/22/21 9:57 PM, Tim Cross wrote:
> William McCoy <wdm8588@gmail.com> writes:
>
>> I am modifying my previous message (that has not yet appeared on this list) with
>> some additional information regarding this issue:
>>
>>
>> I have been having some strange errors when using org-agenda.  The errors seem
>> to have begun about the time I upgraded to org 9.5 from the elpa repo a couple
>> of weeks ago.  When I activate org-agenda, I get the usual menu.  When I press
>> 'm' to search for a tag and then enter a known tag name, I get an empty *Org
>> Agenda* buffer and an error in the minibuffer:
>>
>>
>>
>> Symbol’s value as variable is void: timestamp-up
>>
>>
>> With debug-on-error set, I get the following backtrace:
>>
>>
>> Debugger entered--Lisp error: (void-variable timestamp-up)
>>    org-entries-lessp(#("  ubuntu:     Updated Pop_OS (Ubuntu) ..." 0 14 (type
>> "tagsmatch" priority 1000 ts-date nil todo-state$
>>    sort((... ... ... ... ... ... ... ... ... ... ... ... ... ... ...)
>> org-entries-lessp)
>>    org-agenda-finalize-entries((... ... ... ... ... ... ... ... ... ... ... ...
>> ... ... ...) tags)
>>    org-tags-view(nil)
>>    funcall-interactively(org-tags-view nil)
>>    call-interactively(org-tags-view)
>>    org-agenda(nil)
>>    funcall-interactively(org-agenda nil)
>>    call-interactively(org-agenda nil nil)
>>    command-execute(org-agenda)
>>
>> When I enter org-agenda and use 'a' for my agenda, I get the following error:
>>
>>
>> Invalid function: (date date)
>>
>>
>> And the backtrace is:
>>
>>
>> Debugger entered--Lisp error: (invalid-function (date date))
>>    (date date)()
>> org-agenda-get-day-entries("/home/wdmccoy/orgfiles/C/C-examples.org" (10 18
>> 2021) :deadline :scheduled :timestamp :sexp)
>>    apply(org-agenda-get-day-entries "/home/wdmccoy/orgfiles/C/C-examples.org" (10
>> 18 2021) (:deadline :scheduled :timestamp :s$
>>    org-agenda-list(nil)
>>    funcall-interactively(org-agenda-list nil)
>>    call-interactively(org-agenda-list)
>>    org-agenda(nil)
>>    funcall-interactively(org-agenda nil)
>>    call-interactively(org-agenda nil nil)
>>    command-execute(org-agenda)
>>
>>
>> Disregard the following comments between the dashed lines.  I just realized that
>> when I start emacs with the -Q switch, an older built-in version of org-mode
>> (9.4.4) is used.  So I do think this is related to changes in version 9.5.
>>
>> --------------------------------------------------------------------------
>> If I start  emacs with the -Q switch and then execute my org-agenda-files
>> setting command in the *scratch* buffer:
>>
>>
>> (setq org-agenda-files (directory-files-recursively "~/orgfiles/" "\\.org$"))
>>
>>
>> then org-agenda appears to work fine without errors.
>> --------------------------------------------------------------------------
>>
>>
>> I have made a minimal init.el file and trimmed virtually everything from my
>> emacs-custom.el file (file attached), but the error still occurs.  I just can't
>> figure out what's causing it.  Any ideas?
>>
>> Also I forgot to add:
>>
>> emacs-version: GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version
>> 3.24.20, cairo version 1.16.0) of 2021-06-04
>>
>> org-version: Org mode version 9.5 (9.5-g0a86ad @
>> /home/wdmccoy/.emacs.d/elpa/org-9.5/)
>>
>> OS:  Linux pop-os 5.13.0-7614-generic #14~1631647151~21.04~930e87c-Ubuntu SMP
>>
>>
>> Thanks, Bill
>>
>>
>>
>> [2. text/x-emacs-lisp; init.el]...
>>
>> [3. text/x-emacs-lisp; emacs-custom.el]...
> These types of errors are frequently caused by a 'mixed' installation of
> org versions. This will happen if you upgrade org when org is already
> loaded in the instance of emacs used to perform the upgrade.
>
> It is critically important when upgrading org that org is not already
> loaded. Highly recommend you remove the version of org you have
> installed, restart emacs (ensuring nothing in your init.el loads org -
> comment out if there is), install org 9.5, uncomment anything in your
> init.el you commented to ensure org was not loaded, restart emacs and
> see if the problem is resolved.
>
> Note that if your installing other org extensions, make sure these are
> not loaded as well as it is probable they will load org as well.
>