emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Morgan Smith <Morgan.J.Smith@outlook.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-encode-time bug
Date: Sat, 23 Jul 2022 10:03:59 +0800	[thread overview]
Message-ID: <875yjopots.fsf@localhost> (raw)
In-Reply-To: <DM5PR03MB316345C2708C05540A85016EC5919@DM5PR03MB3163.namprd03.prod.outlook.com>

Morgan Smith <Morgan.J.Smith@outlook.com> writes:

> I'm using emacs from commit f258f67 (quite recent) and org from commit
> 39005dc (quite recent).
>
> I'm using native compilation and PGTK.

> Debugger entered--Lisp error: (invalid-function org-encode-time)
>   org-encode-time((0 0 0 21 7 2022 4 t -14400))
>   org-matcher-time("<2022-07-21 Thu 00:00>")
>   org-clock-get-table-data(...)
>   org-dblock-write:clocktable(...)
>   org-update-dblock()
>   org-ctrl-c-ctrl-c(nil)
>   funcall-interactively(org-ctrl-c-ctrl-c nil)
>   command-execute(org-ctrl-c-ctrl-c)

org-encode-time is defined in org-macs.el in the latest Org, but _not_
in built-in Org. What you are seeing is most likely caused by "mixed"
installation of Org when part of Org is loaded from built-in Org
distribution coming from Emacs.

> I was able to reproduce this with 'emacs -Q'
>
> When trying to update a clocktable I get the following backtrace (with a
> little bit removed).

Could you please detail on what you did to load the latest org with
Emacs -Q? Using purely emacs -Q cannot trigger the error simply because
org-encode-time is absent in the built-in Org.

Best,
Ihor


  reply	other threads:[~2022-07-23  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 20:54 org-encode-time bug Morgan Smith
2022-07-23  2:03 ` Ihor Radchenko [this message]
2022-07-25 13:24   ` Nick Dokos
2022-08-18 12:53   ` Morgan Smith

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yjopots.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=Morgan.J.Smith@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).