From: Eduardo Bellani <eduardo.bellani@datarisk.io>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]
Date: Wed, 10 Mar 2021 12:58:44 -0300 [thread overview]
Message-ID: <87y2ev9ez5.fsf@datarisk.io> (raw)
In-Reply-To: <87r1knaazf.fsf@kyleam.com>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
This was a wrong bug report, you can ignore.
Looking at `list-load-path-shadows` and poking around my config
indicated a mixed installation.
Thanks Kyle!
Kyle Meyer writes:
> Eduardo Bellani writes:
>
>> Kyle Meyer writes:
>>
>>> In 16b5ee0ef, org-clocking-buffer was moved from org-clock.el to org.el,
>>> and org-clock.el loads org.el.
>>>
>>> What's the concrete problem that you're running into?
>
>> Backtrace:
>>
>> Debugger entered--Lisp error: (void-function org-clocking-buffer)
>> org-clocking-buffer()
>> org-clocking-p()
>> org-clock-in(nil)
>> funcall-interactively(org-clock-in nil)
>> call-interactively(org-clock-in nil nil)
>> command-execute(org-clock-in)
>
> My guess is that you either have a stale org.elc file or have a mixed
> installation with an old org.el shadowing the new one. If the issue
> doesn't go away after removing/regenerating the elc files,
> list-load-path-shadows might reveal the problem.
>
> https://orgmode.org/worg/org-faq.html#mixed-install
--
Eduardo Bellani -- datarisk.io
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
prev parent reply other threads:[~2021-03-10 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 17:15 Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3] Eduardo Bellani
2021-03-09 5:40 ` Kyle Meyer
2021-03-09 15:48 ` Eduardo Bellani
2021-03-10 4:28 ` Kyle Meyer
2021-03-10 15:58 ` Eduardo Bellani [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2ev9ez5.fsf@datarisk.io \
--to=eduardo.bellani@datarisk.io \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.