Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]

Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]

[Eduardo Bellani]

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

On 16b5ee0efb5592f78faeffa07048bfe741331a18 `org-clocking-buffer` was
removed as a symbol. That symbol is still being referenced throughout
the current(4d463ee4baf8a7ce8b7c633149a9452bc70ef557) `org-clock.el`
file.


Emacs  : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5, cairo version 1.16.0)
 of 2020-12-25
Package: Org mode version 9.4.3

--
Eduardo Bellani -- datarisk.io

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 873 bytes --]

Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]

[Kyle Meyer]

Eduardo Bellani writes:

> On 16b5ee0efb5592f78faeffa07048bfe741331a18 `org-clocking-buffer` was
> removed as a symbol. That symbol is still being referenced throughout
> the current(4d463ee4baf8a7ce8b7c633149a9452bc70ef557) `org-clock.el`
> file.

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?

Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]

[Eduardo Bellani]

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

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)

Kyle Meyer writes:

> Eduardo Bellani writes:
>
>> On 16b5ee0efb5592f78faeffa07048bfe741331a18 `org-clocking-buffer` was
>> removed as a symbol. That symbol is still being referenced throughout
>> the current(4d463ee4baf8a7ce8b7c633149a9452bc70ef557) `org-clock.el`
>> file.
>
> 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?


--
Eduardo Bellani -- datarisk.io

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 873 bytes --]

Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]

[Kyle Meyer]

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

Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]

[Eduardo Bellani]

[-- 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 --]