From: Ian Garmaise <firstname.lastname@example.org>
To: emacs-orgmode <email@example.com>
Subject: Re: Bug: Missing key definition for org-resolve-clocks [9.3.6 (9.3.6-25-g685b2c-elpa @ c:/users/ian/.emacs.d/elpa/org-20200316/)]
Date: Wed, 6 May 2020 06:18:45 -0400 [thread overview]
Message-ID: <CALWEx6X8vDB5xENct8GTc6YrM+E+n8D9nPdfRyMuZ4WuLfF7VA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
Not sure what happened, but about a month after I reported it, the key
binding started to work.
I hadn't made significant changes to my setup during that period, but maybe
some library that I had installed caused the problem.
Thanks for checking,
On Tue, May 5, 2020 at 11:38 PM Kyle Meyer <firstname.lastname@example.org> wrote:
> [ Sorry for the delayed reply. ]
> Ian Garmaise writes:
> > According to the manual section 8.4.3, org-resolve-clocks should be
> > bound to C-c C-x C-z
> > This doesn't seem to be the case.
> That's odd. That binding has been around for a while (f250f6beb,
> 2012-07-28) and is in the version you reported to be running:
> $ git grep org-resolve-clocks 685b2c -- lisp/org-keys.el
> 685b2c:lisp/org-keys.el:(declare-function org-resolve-clocks "org"
> (&optional only-dangling-p prompt-fn last-valid))
> 685b2c:lisp/org-keys.el:(org-defkey org-mode-map (kbd "C-c C-x C-z")
> Perhaps there's something in your configuration that's clobbering the
> default binding.
Phorix Solutions Group
Toronto cell: 416.432.2251
[-- Attachment #2: Type: text/html, Size: 2912 bytes --]
prev parent reply other threads:[~2020-05-06 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 13:55 Bug: Missing key definition for org-resolve-clocks [9.3.6 (9.3.6-25-g685b2c-elpa @ c:/users/ian/.emacs.d/elpa/org-20200316/)] Ian Garmaise
2020-05-06 3:38 ` Kyle Meyer
2020-05-06 10:18 ` Ian Garmaise [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).