not top level in wrap-native

[indigoviolet]

Explain-pause-mode: please report this bug by creating a Github issue at https://github.com/lastquestion/explain-pause-mode. Explain-pause-mode is now disabled so you can continue to hopefully use Emacs. Info follows:

explain-pause version: 0.1 emacs version: 29.0.50

not top level in wrap-native for # current #s(explain-pause-command-record root-emacs nil nil 11959 (25169 6306 870019 417000) nil nil nil nil 0)

Backtrace: explain-pause-report-measuring-bug("not top level in wrap-native for #<subr read-event..." "current" #s(explain-pause-command-record :command root-emacs :native nil :parent nil :executing-time 11959 :entry-snap (25169 6306 870019 417000) :too-slow nil :is-profiled nil :under-profile nil :profile nil :depth 0)) explain-pause--wrap-native(# nil t 0.3) apply(explain-pause--wrap-native # (nil t 0.3)) read-event(nil t 0.3) sit-for(0.3 no-redisplay) key-chord-input-method(104)

[indigoviolet]

@lastquestion , is this still active? any prospect of getting it to work with native-comp?

[nullman]

I also got this error:

Explain-pause-mode: please report this bug by creating a Github issue at https://github.com/lastquestion/explain-pause-mode. Explain-pause-mode is now disabled so you can continue to hopefully use Emacs. Info follows:

explain-pause version: 0.1 emacs version: 28.1

not top level in wrap-native for # current #s(explain-pause-command-record root-emacs nil nil 2337797 (25289 46981 178396 927000) nil nil nil nil 0)

Backtrace: explain-pause-report-measuring-bug("not top level in wrap-native for #<subr read-event..." "current" #s(explain-pause-command-record :command root-emacs :native nil :parent nil :executing-time 2337797 :entry-snap (25289 46981 178396 927000) :too-slow nil :is-profiled nil :under-profile nil :profile nil :depth 0)) explain-pause--wrap-native(# nil t 0.1) apply(explain-pause--wrap-native # (nil t 0.1)) read-event(nil t 0.1) sit-for(0.1 no-redisplay) key-chord-input-method(51)

[jeffkowalski]

I see the same

Explain-pause-mode: please report this bug by creating a Github
issue at https://github.com/lastquestion/explain-pause-mode. Explain-pause-mode
is now _disabled_ so you can continue to hopefully use Emacs. Info follows:

explain-pause version: 0.1
emacs version: 28.1

not top level in wrap-native for #<subr read-event>
current
#s(explain-pause-command-record root-emacs nil nil 55148 (25309 61811 105975 363000) nil nil nil nil 0)

Backtrace:
  explain-pause-report-measuring-bug("not top level in wrap-native for #<subr read-event..." "current" #s(explain-pause-command-record :command root-emacs :native nil :parent nil :executing-time 55148 :entry-snap (25309 61811 105975 363000) :too-slow nil :is-profiled nil :under-profile nil :profile nil :depth 0))
  explain-pause--wrap-native(#<subr read-event> nil t 0.1)
  apply(explain-pause--wrap-native #<subr read-event> (nil t 0.1))
  read-event(nil t 0.1)
  sit-for(0.1 no-redisplay)
  key-chord-input-method(120)

I invoke it from my doom-emacs config, using this, which is executed at startup.

(use-package! explain-pause-mode
  :config
  (explain-pause-mode))

I've also uploaded my doom info in case that's helpful.