From 8fa16f616c4ae963f77febe30e6aa167f389b162 Mon Sep 17 00:00:00 2001 From: Daniel Eklöf Date: Wed, 16 Feb 2022 22:40:51 +0100 Subject: main: --server: don’t exit with code 0 on failure MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A foot --server instance would exit with code 0, even on failure, if the number of currently open terminal instances were 0. This is because ‘ret’ assumed failure, and then tried to set it to ‘success’ after the even loop had terminated, basted on the server’s current state. Fix by: * set ‘ret’ to success just before entering the event loop * set ‘ret’ to failure when we detect an FDM failure * don’t try to second-guess success/failure after having exited the event loop Closes #943 --- main.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'main.c') diff --git a/main.c b/main.c index ff839507..4011dcde 100644 --- a/main.c +++ b/main.c @@ -642,14 +642,14 @@ main(int argc, char *const *argv) goto out; } + ret = EXIT_SUCCESS; while (likely(!aborted && (as_server || tll_length(wayl->terms) > 0))) { - if (unlikely(!fdm_poll(fdm))) + if (unlikely(!fdm_poll(fdm))) { + ret = foot_exit_failure; break; + } } - if (aborted || tll_length(wayl->terms) == 0) - ret = EXIT_SUCCESS; - out: free(_cwd); server_destroy(server); -- cgit v1.3