Michael Ziems <address@hidden> writes:
thanks for the reply. is this information already helpful:
- command-execute 1331 92%
- call-interactively 1327 91%
- org-shiftdown 302 20%
- call-interactively 302 20%
- org-priority-down 302 20%
org-priority 302 20%
- org-shiftup 293 20%
- call-interactively 293 20%
- org-priority-up 293 20%
org-priority 293 20%
- next-line 183 12%
- funcall 183 12%
- #<compiled 0xc28a69> 183 12%
- line-move 183 12%
line-move-visual 180 12%
- org-cycle 145 10%
- org-cycle-internal-local 145 10%
- run-hook-with-args 108 7%
- org-optimize-window-after-visibility-change 104 7%
- org-subtree-end-visible-p 8 0%
- pos-visible-in-window-p 6 0%
- jit-lock-function 6 0%
- jit-lock-fontify-now 6 0%
+ funcall 6 0%
+ org-cycle-hide-archived-subtrees 2 0%
+ org-cycle-show-empty-lines 2 0%
+ show-children 34 2%
+ org-agenda 138 9%
+ previous-line 120 8%
+ byte-code 76 5%
+ find-file 31 2%
+ save-buffer 19 1%
+ org-shiftleft 15 1%
+ execute-extended-command 3 0%
+ org-shiftright 2 0%
- autoload-do-load 3 0%
I don't see anything suspicious. Can you try using ELP (see
`elp-instrument-package') to instrument org package?
Regards,