From: Patrick Useldinger <uselpa@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Emacs-orgmode@gnu.org
Subject: Re: [BUG] org-capture, level-2 heading, org-set-tags-command [9.6.6 ( @ /Users/pu/.emacs.d/elpa/org-9.6.6/)]
Date: Tue, 23 May 2023 11:13:05 +0200 [thread overview]
Message-ID: <38eff201-0e24-5cd5-979b-7044726ae228@gmail.com> (raw)
In-Reply-To: <87o7mfoup8.fsf@localhost>
On 20/05/2023 18:04, Ihor Radchenko wrote:
> I am unable to reproduce.
> Could you please try to detail all the steps more precisely, starting
> from emacs -Q?
>
I have been able to create a minimal set of init.el and WORK.org which
allows me to reproduce the problem:
1) start Emacs
2) F6 (shortcut for capture)
3) x
4) create a task in the capture buffer
5) press C-c C-q and enjoy the loop
6) C-g breaks the loop
OTOH, using t at step 3 works well.
As indicated, the only difference between the remplates x and t is that
x uses 2 levels of heading, whereas t only uses one.
--- WORK.org
;; -*- coding: utf-8 -*-
#+TODO: WAIT(w) TODO(t) DELG(d) | DONE(x)
#+STARTUP: show2levels hidestars nologrepeat
#+ARCHIVE: %s_archive::
* CAPTURE
** Regulars
*** TODO [#C] -- Empty CAP.org/CAPTURE
SCHEDULED: <2023-05-26 Fri ++1w>
** Cap-X
** WAIT hello
:test:
** DONE read "acceptable use"
DEADLINE: <2023-05-19 Fri>
--- init.el
;; custom variables
(custom-set-variables
;; custom-set-variables was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
'(org-capture-templates
'(("x" "Todo (test)" entry
(file+olp "/Users/pu/Workcloud/org/WORK.org" "CAPTURE" "Cap-X")
"* TODO %^{Task Description}" :prepend t)
("t" "Todo (work)" entry
(file+olp "~/Workcloud/org/WORK.org" "CAPTURE")
next prev parent reply other threads:[~2023-05-23 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 15:47 [BUG] org-capture, level-2 heading, org-set-tags-command [9.6.6 ( @ /Users/pu/.emacs.d/elpa/org-9.6.6/)] Patrick Useldinger
2023-05-20 16:04 ` Ihor Radchenko
2023-05-20 18:41 ` Patrick Useldinger
2023-05-20 20:01 ` Ihor Radchenko
2023-05-20 21:06 ` Patrick Useldinger
2023-05-22 8:35 ` Ihor Radchenko
2023-05-21 9:00 ` Patrick Useldinger
2023-05-23 9:07 ` Patrick Useldinger
2023-05-23 9:15 ` Patrick Useldinger
2023-05-23 9:15 ` Patrick Useldinger
2023-05-24 8:56 ` Ihor Radchenko
2023-05-23 9:13 ` Patrick Useldinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 21:23 Patrick Useldinger
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=38eff201-0e24-5cd5-979b-7044726ae228@gmail.com \
--to=uselpa@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).