emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: long delay after selecting capture template
Date: Sat, 19 Mar 2016 21:38:47 +0800	[thread overview]
Message-ID: <87lh5eoae0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87zitvk6dp.fsf@viking.dsc.soic.indiana.edu

Allan Streib <astreib@indiana.edu> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I guess I would `toggle-debug-on-quit', then call capture, and while
>> you're waiting for it to return, hit "C-g". That ought to pop up a
>> backtrace, and you can see what code was being executed during the
>> delay. It might be obvious what's wrong, or you can post the backtrace
>> here.
>
> I tried this but get no backtrace. Messages buffer contains:
>
>
> Debug on Quit enabled globally
> Template key: 
> byte-code: Capture abort: (quit)

Ah, the org-capture code condition-cases quit. At least we know that the
problem is in `org-capture-fill-template'!

I can't remember off the top of my head if there's a way to tell emacs
to actually debug on quit, even if quit is handled by `condition-case'.

Another thing you can try is edebugging `org-capture-fill-template' and
stepping through it, and just see if anything weird happens. See the
Elisp manual for how to edebug, if you haven't before.

Does it only happen for the "t" template? What's the "t" template look
like?

Eric

  reply	other threads:[~2016-03-19 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 17:10 long delay after selecting capture template Allan Streib
2016-03-17 23:53 ` Eric Abrahamsen
2016-03-18 18:09   ` Allan Streib
2016-03-19 13:38     ` Eric Abrahamsen [this message]
2016-03-24 13:27       ` Allan Streib
2016-03-24 13:40         ` Eric Abrahamsen
2016-03-24 14:07         ` Eric S Fraga
2016-03-24 14:36           ` Allan Streib

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=87lh5eoae0.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).