5fb5984e94
Prior to this patch, if I ran something like this, sway would crash:
swaymsg bar height 50
or
swaymsg bar not-a-bar-id color bg #ff0000
This was in contrast to other bar subcommands, like status_command,
which would exit with a "No bar defined" message.
The difference between the subcommands that crashed and the ones that
exited was that some subcommands had a check to see if a bar was
specified, while others just assumed that it had been and carried on
until they segfaulted.
Because this check was identical in every subcommand it was present in,
and I couldn't think of a case where it would be valid to run a bar
subcommand without specifying which bar to apply it to, I moved this
check from individual subcommands into the bar command, which is already
responsible for actually setting the specified bar. This reduced code
duplication, and fixed the crash for the subcommands that were missing
this check.
17 lines
538 B
C
17 lines
538 B
C
#include <string.h>
|
|
#include "sway/commands.h"
|
|
#include "log.h"
|
|
#include "stringop.h"
|
|
|
|
struct cmd_results *bar_cmd_swaybar_command(int argc, char **argv) {
|
|
struct cmd_results *error = NULL;
|
|
if ((error = checkarg(argc, "swaybar_command", EXPECTED_AT_LEAST, 1))) {
|
|
return error;
|
|
}
|
|
free(config->current_bar->swaybar_command);
|
|
config->current_bar->swaybar_command = join_args(argv, argc);
|
|
sway_log(SWAY_DEBUG, "Using custom swaybar command: %s",
|
|
config->current_bar->swaybar_command);
|
|
return cmd_results_new(CMD_SUCCESS, NULL);
|
|
}
|