emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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:15:51 +0200	[thread overview]
Message-ID: <CANv=RK4+2Qd+ugX9mQdgsQo=_TGqOqczoAqKPTV7Y1Byf_c8oQ@mail.gmail.com> (raw)
In-Reply-To: <87lehipyan.fsf@localhost>

On 20/05/2023 22:01, Ihor Radchenko wrote:
> You can try to bisect your config to identify which part is triggering
> the problem. See
> https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
> https://github.com/Malabarba/elisp-bug-hunter

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) create a task in the capture buffer
4) press C-c C-q and enjoy the loop
5) C-g breaks the loop

--- WORK.org

;; -*- coding: utf-8 -*-
#+TODO: WAIT(w) TODO(t) DELG(d) | DONE(x)
#+STARTUP: show2levels hidestars nologrepeat
#+ARCHIVE: %s_archive::
** Regulars
*** TODO [#C] -- Empty CAP.org/CAPTURE
     SCHEDULED: <2023-05-26 Fri ++1w>
** Cap-X
** WAIT hello
** DONE read "acceptable use"
    DEADLINE: <2023-05-19 Fri>

--- init.el

;; custom 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.
    '(("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")
       "* TODO %^{Task Description}" :prepend t)
      ("n" "Note (work)" entry
       (file+olp "~/Workcloud/org/WORK.org" "CAPTURE")
       "* %^{Note Description}" :prepend t))))

;; system-specific
(when (eq system-type 'darwin)
   (setq ns-alternate-modifier 'meta)
   (setq ns-right-alternate-modifier nil))

;; package: org
  (lambda ()
    (define-key org-mode-map "\C-ca" 'org-agenda)
     (lambda ()
       (define-key org-agenda-mode-map "\M-p" 'org-agenda-backward-block)
       (define-key org-agenda-mode-map "\M-n" 'org-agenda-forward-block)))
    (global-set-key (kbd "<f6>") 'org-capture)))

(defun pu/options ()
(add-hook 'window-setup-hook 'pu/options)

(defun pu/option-org ()
   (find-file "~/Workcloud/org/WORK.org"))

  parent reply	other threads:[~2023-05-23  9:17 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 [this message]
2023-05-24  8:56         ` Ihor Radchenko
2023-05-23  9:13   ` Patrick Useldinger
  -- 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:

  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='CANv=RK4+2Qd+ugX9mQdgsQo=_TGqOqczoAqKPTV7Y1Byf_c8oQ@mail.gmail.com' \
    --to=uselpa@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


* 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).