Doom sandbox modes (vanilla or + modules) don't work

[indigoviolet]

What did you expect to happen?

When I hit doom/sandbox -> C-c C-d or C-c C-p, it should load a functional emacs.

What actually happened?

Instead I got

Debugger entered--Lisp error: (void-function doom-initialize)
  (doom-initialize)
  (let ((doom-init-modules-p t)) (doom-initialize) (doom-initialize-core-modules))
  load-with-code-conversion("/tmp/doom-sandbox/init.el" "/tmp/doom-sandbox/init.el" nil t)
  command-line-1(("-l" "/tmp/doom-sandbox/init.el"))
  command-line()
  normal-top-level()

Describe your attempts to resolve the issue

I've upgraded doom to a fairly recent version.

Steps to reproduce

1. Open doom emacs
2. doom/sandbox
3. C-c C-d or C-c C-p

Note that I'm using chemacs2 with

(
 ;; Doom. These are its defaults, and it's better to use them for doom/sandbox etc to work
 ("default" . ((user-emacs-directory . "~/.emacs.d")
               (env . (("DOOMDIR" . "~/.config/doom")))))
 )

System Information

https://pastebin.com/HQr07pC1

[workcomplete]

Having the same issue using doom emacs on KDE/arch

[aikrahguzar]

It seems that doom--sandbox-run needs a rewrite. doom-initialize is now gone and I think elisp file in doom-core have been split/reorganized. Removing calls to doom-initialize and then adding calls to load core-packages.el and core-modules.el allows to C-c C-d to complete without error but then I do get bindings from my private config so issues with it run deeper.

[xeruf]

yes, this makes it hard to debug issues :/

[NightMachinery]

Is there a way to start Doom without the private config using CLI flags?

[xeruf]

temporarily move away your doom config folder I guess