From 4db57bf5bd788a292fcf2cfbea3b6d8b281510f0 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Thu, 1 Oct 2026 10:31:23 -0300 Subject: Saving the init file in a pane (Config) applies its settings at once; its commands are not run a second time A setting changed in the init file took effect only at the next start. The host's Save now hands a written init file's text back to the core, which applies its setting lines again (each idempotent), with the same notice and err for one that fails; a command line in it (`Newcol`) belongs to the start and is left alone. Co-Authored-By: Claude Opus 5.5 --- src/host_io.zig | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/host_io.zig') diff --git a/src/host_io.zig b/src/host_io.zig index a488f0f8..8ff55d74 100644 --- a/src/host_io.zig +++ b/src/host_io.zig @@ -2818,6 +2818,8 @@ pub fn writeFile(core: *pardes.Pardes, watches: *file_watch.Table, pane: u8, pat }; var mbuf: [256]u8 = undefined; core.setMessage(pane, pardes.Messages.Message.stamp(&mbuf, "saved", path)); + // The init file, saved here (Config): its settings take effect now. + pardes.exec.reapplyInitFile(core, path, bytes); } /// A Dump's write, into the DumpDir. -- cgit v1.3