From: Max Nikulin <manikulin@gmail.com>
To: Ignacio Casso <ignaciocasso@hotmail.com>, emacs-orgmode@gnu.org
Cc: c.buhtz@posteo.jp
Subject: Re: [BUG] org-capture autoload bug? [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)]
Date: Thu, 10 Mar 2022 23:32:56 +0700 [thread overview]
Message-ID: <f2e22125-2c38-a9af-1806-68426443e1af@gmail.com> (raw)
In-Reply-To: <PAXPR06MB77602E75E066A63577E6972FC60B9@PAXPR06MB7760.eurprd06.prod.outlook.com>
On 10/03/2022 19:53, Ignacio Casso wrote:
> For example, if we call this:
>
> (let ((org-capture-templates
> '(("d" "default" entry
> (file+headline org-default-notes-file "Tasks")
> "* %?"))))
> (org-capture nil "d")))
>
> It produces the error:
>
> (error "No capture template referred to by \"d\" keys")
Ignacio, could you, please, try the following?
(custom-set-variables
'(org-capture-templates
'(("d" "default" entry
(file "/tmp/capture-test.org")
"* %?"))))
(org-capture nil "d")
On 09/03/2022 23:39, c.buhtz wrote in
https://list.orgmode.org/7395938a0e6b06139239bc70ba7c2b19@posteo.de:>
Why using custom-set variables here? Is there something wrong with just
doing
> (org-export-with-broken-links t)
> ?
I do not think that something similar may happen with
`org-export-with-broken-links', but I suppose, the example above is
another argument to prefer setting variables through customization
interface instead of bare `setq' in general.
next prev parent reply other threads:[~2022-03-10 16:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 12:53 [BUG] org-capture autoload bug? [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)] Ignacio Casso
2022-03-10 16:32 ` Max Nikulin [this message]
2022-03-10 18:00 ` Ignacio Casso
2022-03-11 10:07 ` Max Nikulin
2022-03-11 10:38 ` Ignacio Casso
2022-03-11 19:59 ` Tim Cross
2022-03-14 10:42 ` Ignacio Casso
2022-03-14 14:52 ` Max Nikulin
2022-03-14 18:42 ` Tim Cross
2022-03-14 19:43 ` Ignacio Casso
2022-03-14 22:54 ` Tim Cross
2022-03-15 9:02 ` Ignacio Casso
2022-03-15 15:59 ` Ignacio Casso
2022-03-15 12:04 ` Max Nikulin
2022-03-15 12:26 ` Ignacio Casso
-- strict thread matches above, loose matches on Subject: below --
2022-06-11 7:50 Ignacio Casso
2022-06-11 13:32 ` Ihor Radchenko
2022-06-11 17:25 ` Ignacio Casso
2022-06-14 4:02 ` Ihor Radchenko
2022-06-14 7:49 ` Ignacio Casso
2022-06-14 13:58 ` Ihor Radchenko
2022-06-12 12:36 ` Max Nikulin
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=f2e22125-2c38-a9af-1806-68426443e1af@gmail.com \
--to=manikulin@gmail.com \
--cc=c.buhtz@posteo.jp \
--cc=emacs-orgmode@gnu.org \
--cc=ignaciocasso@hotmail.com \
/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).