Eric S Fraga writes:
> I've had this problem in the past. I found that setting this variable helps:
>
> ,[ C-h v x-selection-timeout RET ]
> | x-selection-timeout is a variable defined in ‘C source code’.
> | Its value is 10
> |
> | Documentation:
> | Number of milliseconds to wait for a sel
On Thursday, 24 Mar 2016 at 09:27, Allan Streib wrote:
[...]
> Debugging the function, the "stall" happens on the indicated line below,
> the call to org-get-x-clipboard with the value 'SECONDARY
[...]
> I've heard of primary and clipboard X11 selections, but not secondary. I
> found a web post
Allan Streib writes:
> Eric Abrahamsen writes:
>
>> 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" temp
Eric Abrahamsen writes:
> 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 l
Eric Abrahamsen 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 b
Allan Streib writes:
> Hi,
>
> When I want to capture a task I hit C-c c and then t to select the task
> template.
>
> Between striking the t key and seeing the template rendered, there is a
> delay of several seconds (sometimes up to 10 seconds). No errors are
> logged and the template eventuall
Hi,
When I want to capture a task I hit C-c c and then t to select the task
template.
Between striking the t key and seeing the template rendered, there is a
delay of several seconds (sometimes up to 10 seconds). No errors are
logged and the template eventually displays and everything is normal.
Allan Streib writes:
> Eric Abrahamsen 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'
