Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]
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 signature.asc Description: PGP signature
Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]
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]
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 signature.asc Description: PGP signature
Re: Bug: 28.0.50; `org-clocking-buffer` definition was removed, but it is still being referenced [9.4.3]
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?
