emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Trouble with capture template and prompt
Date: Wed, 14 Sep 2016 09:48:11 -0400	[thread overview]
Message-ID: <87eg4m1tk4.fsf@gmail.com> (raw)
In-Reply-To: m27faead5p.fsf@fiz.local

Bart Bunting <bart@bunting.net.au> writes:

> Adam,
>
> I sort of had already narrowed it down but am unsure of how to debug
> further.
>
> Removing %^{Todo}  from the template and everything works.
>
> Of course the thing that doesn't work is that org no longer prompts me
> for the title of the task to create which makes me sad :).
>
> Any suggestions on how to dig into this further?
>
> Here is the output when debug-on-error is set to t:
>
> Debugger entered--Lisp error: (error "Capture abort: (error Key sequence C-c ! starts with non-prefix key C-c)")
>   signal(error ("Capture abort: (error Key sequence C-c ! starts with non-prefix key C-c)"))
>   error("Capture abort: %s" (error "Key sequence C-c ! starts with non-prefix key C-c"))
>   org-capture(nil)
>   #<subr funcall-interactively>(org-capture nil)
>   apply(#<subr funcall-interactively> org-capture nil)
>   ad-Advice-funcall-interactively(#<subr funcall-interactively> org-capture nil)
>   apply(ad-Advice-funcall-interactively #<subr funcall-interactively> (org-capture nil))
>   funcall-interactively(org-capture nil)
>   #<subr call-interactively>(org-capture nil nil)
>   ad-Advice-call-interactively(#<subr call-interactively> org-capture nil nil)
>   apply(ad-Advice-call-interactively #<subr call-interactively> (org-capture nil nil))
>   call-interactively(org-capture nil nil)
>   command-execute(org-capture)
>
See if you can get a backtrace with uncompiled code: it is much more informative.
See

  (info "(org) Feedback")

in particular the section "How to create a useful backtrace".

> I have some other bits of org config in my main config file but not sure
> that they would cause breakage like this.
>
> The other thing is that I use emacspeak which is probably the advice
> calls shown in the debug above.  Hard for me to test without it though
> as then I can't use emacs.
>
> Could try ripping out almost all of the org config and see if that
> helps.
>
> I could also try an earlier version of emacspeak in case the error is
> being caused by the advice in some strange way.
>

-- 
Nick

  reply	other threads:[~2016-09-14 13:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 13:32 Trouble with capture template and prompt Bart Bunting
2016-09-12 23:17 ` Adam Porter
2016-09-13 20:00   ` Bart Bunting
2016-09-14  4:47     ` Adam Porter
2016-09-14 12:17       ` Bart Bunting
2016-09-14 13:48         ` Nick Dokos [this message]
2016-09-15 16:57         ` Adam Porter
  -- strict thread matches above, loose matches on Subject: below --
2016-09-06 10:20 Bart Bunting

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=87eg4m1tk4.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).