From: Neil Shephard <email@example.com>
Subject: Org-capture template no longer recognised...
Date: Mon, 4 Jan 2021 22:42:10 +0000 [thread overview]
Message-ID: <CADcCPCH85YxpJDXXAc4ZvuF-DtT8t+vOoQVxW5dxCdbVcZoOvw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4399 bytes --]
I am enjoying learning more and more about how functional and useful
org-mode is, truly amazing software.
One thing I've setup is a Babel document for logging exercise activities
and accompanying custom org-capture-templates for entering data. These
worked great until recently but with no conscious change to my
org-capture-template they are now broken.
A simple example of the document is ~/org/training/training.org
#+CAPTION: Running Log
| Date | Route | Distance | Time |
Pace | Notes |
| <2021-01-03 Fri> | Shorter 12km run | 12.25km | 60min + 25s | 4
min / km + 55.918367 s / km | Less icey! |
| <2021-01-01 Fri> | Longer 16km run | 16.22km | 80min + 03s | 4
min / km + 56.115906 s / km | Icey! |
I then have a ~/org/computing.org for keeping notes of tasks to do, a
simple example is...
** TODO <2020-11-11 Wed> vterm only on non-work computers.
My org-capture-templates are...
("ce" "Emacs" entry (file+olp "~/org/computing.org" "Emacs")
"* TODO %t %?\n" :prepend t)
("er" "Logging a run" table-line (file+olp
"~/org/training/training.org" "Running" "Log")
"| %t | %? | km | min + s | | |" :prepend t)
("ec" "Logging a cycle" table-line (file+olp
"~/org/training/training.org" "Cycling" "Log")
"| %t | %? | km | min + s | | |" :prepend t)))
Until recently I could invoke org-capture, select e r and I'd be
prompted to enter data under Route...
| <2021-01-03 | <cursor here to start entry> | km | min + s | | |
On saving this would populate the table and calculate the pace. Now
though I'm informed...
Capture abort: Symbol's function definition is void: assert
Debugger entered--Lisp error: (error "Capture abort: Symbol’s function
definition is voi...")
signal(error ("Capture abort: Symbol’s function definition is voi..."))
error("Capture abort: %s" "Symbol’s function definition is void: assert")
org-capture(nil) funcall-interactively(org-capture nil)
call-interactively(org-capture nil nil)
I asked on Emacs Stackexchange
and it was suggested the error lay with cl.el as assert is a function
of this deprecated package. The suggested additional of (require 'cl)
didn't improve things, just got a
different error message...
Debugger entered--Lisp error: (error "Capture abort: Invalid function: assert")
signal(error ("Capture abort: Invalid function: assert"))
error("Capture abort: %s" "Invalid function: assert")
call-interactively(org-capture nil nil)
As I say I'd not changed my configuration which is the org-mode
bundled with Emacs 27.1. I do have
a few computers though and it was still working on a second system
until I update installed packages,
after which the original error messsage (Capture abort: Symbol's
function definition is void: assert)
occurred again. The packages I updated seem unrelated (to my
untrained eye). They were...
What is strange is that capturing to ~/org/computing.org still works fine.
If there is any more information I can provide to assist with working
out where this is occurring
please let me know.
Thanks and regards,
*Ignorance more frequently begets confidence than does knowledge* - Charles
PGP Public : 0x700172212EF5818B
[-- Attachment #2: Type: text/html, Size: 8808 bytes --]
next reply other threads:[~2021-01-04 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 22:42 Neil Shephard [this message]
2021-01-06 4:43 ` Org-capture template no longer recognised Kyle Meyer
2021-01-07 17:57 Neil Shephard
2021-01-08 10:12 ` Ihor Radchenko
2021-01-12 23:44 Neil Shephard
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).