Henrik Lissner

Finally zeroed in on the issue. It should be fixed as of c20c2aa. > By the way, are you able to reproduce the issue on your end, or is it...

What have you set `doom-font` to? (and any of the other `doom-*-font` variables, if any?)

Testing that recipe, org-element.el and `org-element-context` are byte-compiled, so I've failed to reproduce it on 29.2 (without native-comp). It may be an Emacs HEAD issue, but I'll do more testing....

LGTM. Thanks for your help!

This one's a little tricky. better-jumper stores jump history in window parameters (which is preferable/more intuitive to [the alternative](https://github.com/gilbertw1/better-jumper/blob/master/better-jumper.el#L56)), which gets deleted along with windows, so trying to set jump...

As of c0c52f0 this should be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

~~Can [a backtrace](https://discourse.doomemacs.org/t/what-is-a-backtrace-how-to-produce-them/85) be produced from the error? (Not with `emacs --debug-init`, but with enabling debug mode w/ `M-x doom-debug-mode` first, then recreating the error)~~ Nevermind, missed your last statement....

> However, as the error message mentions 1548, I've included lines 1534-1555 too: It's referring to the contents of the buffer `magit-section-post-command-hook` is operating on. I.e. the magit buffer. So...

As of 90070c6 this should be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

Closing because duplicate of #7347. > doom upgrade also throws an error with a 10k lines backtrace @lyndhurst Unrelated issue. See 7769.