Problem statement
GNU Emacs can start with --fg-daemon without creating a graphical frame.
EWM uses that interval to start its in-process Wayland compositor from Lisp, then creates frames on the new display. Neomacs currently builds its winit event loop before Lisp startup, so it exits when no compositor is already available. Could Neomacs defer the Wayland connection and initial native window until a daemon startup hook has run?
Proposed solution
The evaluator and dynamic modules must retain their state when GUI initialization continues.
An acceptance test would start Neomacs with no external Wayland display, start EWM, and map a real Neomacs frame on EWM’s socket.
Alternatives considered
No response
Impact
No response
Platform
None
Extra context
No response
Problem statement
GNU Emacs can start with --fg-daemon without creating a graphical frame.
EWM uses that interval to start its in-process Wayland compositor from Lisp, then creates frames on the new display. Neomacs currently builds its winit event loop before Lisp startup, so it exits when no compositor is already available. Could Neomacs defer the Wayland connection and initial native window until a daemon startup hook has run?
Proposed solution
The evaluator and dynamic modules must retain their state when GUI initialization continues.
An acceptance test would start Neomacs with no external Wayland display, start EWM, and map a real Neomacs frame on EWM’s socket.
Alternatives considered
No response
Impact
No response
Platform
None
Extra context
No response