foot/footclient: use a custom exit code when foot/footclient fail to run

Normally, foot and footclient uses the exit code from the client
application (i.e. the shell).

However, foot (or footclient) itself may fail to run; if run outside
of a Wayland session, or no fonts are installed, or the client
application/shell cannot be found (“foot lsdjfldsjf”) etc.

Up until now, there has been no way to differentiate these kind of
failures from the client application exiting with code 1.

This patch changes foot’s failure exit code to -27/229, and
footclient’s to -28/228. Note that footclient will exit with foot’s
-27/229 if footclient ran successfully, but the foot server failed to
instantiate a new window.

Closes #466.
This commit is contained in:
Daniel Eklöf 2021-04-30 22:47:16 +02:00
parent 29b697a9af
commit a1b41bd186
No known key found for this signature in database
GPG key ID: 5BBD4992C116573F
4 changed files with 33 additions and 18 deletions

View file

@ -312,7 +312,7 @@ fdm_client(struct fdm *fdm, int fd, int events, void *data)
if (instance->terminal == NULL) {
LOG_ERR("failed to instantiate new terminal");
client_send_exit_code(client, -1);
client_send_exit_code(client, -27);
instance_destroy(instance, -1);
goto shutdown;
}
@ -497,7 +497,7 @@ server_destroy(struct server *server)
tll_length(server->clients));
tll_foreach(server->clients, it) {
client_send_exit_code(it->item, 1);
client_send_exit_code(it->item, -27);
client_destroy(it->item);
}