2019-07-16 11:52:22 +02:00
|
|
|
|
#include "config.h"
|
|
|
|
|
|
|
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
|
#include <stdio.h>
|
|
|
|
|
|
#include <string.h>
|
|
|
|
|
|
#include <stdbool.h>
|
2019-07-17 10:12:14 +02:00
|
|
|
|
#include <ctype.h>
|
2019-07-16 11:52:22 +02:00
|
|
|
|
#include <unistd.h>
|
|
|
|
|
|
#include <errno.h>
|
2020-08-27 19:48:13 +02:00
|
|
|
|
#include <pwd.h>
|
|
|
|
|
|
#include <fcntl.h>
|
|
|
|
|
|
|
|
|
|
|
|
#include <sys/types.h>
|
|
|
|
|
|
#include <sys/stat.h>
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
2020-03-12 10:20:05 +01:00
|
|
|
|
#include <linux/input-event-codes.h>
|
2020-03-09 20:03:04 +01:00
|
|
|
|
#include <xkbcommon/xkbcommon.h>
|
2020-07-07 10:44:55 +02:00
|
|
|
|
#include <fontconfig/fontconfig.h>
|
2020-03-09 20:03:04 +01:00
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
#define LOG_MODULE "config"
|
|
|
|
|
|
#define LOG_ENABLE_DBG 0
|
|
|
|
|
|
#include "log.h"
|
2021-01-15 20:39:45 +00:00
|
|
|
|
#include "debug.h"
|
2020-03-09 20:03:04 +01:00
|
|
|
|
#include "input.h"
|
2020-08-07 20:42:34 +01:00
|
|
|
|
#include "macros.h"
|
2020-07-30 18:53:51 +02:00
|
|
|
|
#include "tokenize.h"
|
2020-05-01 11:46:24 +02:00
|
|
|
|
#include "util.h"
|
2020-03-09 20:03:04 +01:00
|
|
|
|
#include "wayland.h"
|
2020-08-04 23:28:16 +01:00
|
|
|
|
#include "xmalloc.h"
|
2020-03-09 20:03:04 +01:00
|
|
|
|
|
2019-07-21 11:06:28 +02:00
|
|
|
|
static const uint32_t default_foreground = 0xdcdccc;
|
|
|
|
|
|
static const uint32_t default_background = 0x111111;
|
|
|
|
|
|
|
|
|
|
|
|
static const uint32_t default_regular[] = {
|
2019-09-21 12:01:29 +02:00
|
|
|
|
0x222222,
|
2019-07-21 11:06:28 +02:00
|
|
|
|
0xcc9393,
|
|
|
|
|
|
0x7f9f7f,
|
|
|
|
|
|
0xd0bf8f,
|
|
|
|
|
|
0x6ca0a3,
|
|
|
|
|
|
0xdc8cc3,
|
|
|
|
|
|
0x93e0e3,
|
|
|
|
|
|
0xdcdccc,
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
static const uint32_t default_bright[] = {
|
2019-08-23 19:42:14 +02:00
|
|
|
|
0x666666,
|
2019-07-21 11:06:28 +02:00
|
|
|
|
0xdca3a3,
|
|
|
|
|
|
0xbfebbf,
|
|
|
|
|
|
0xf0dfaf,
|
|
|
|
|
|
0x8cd0d3,
|
2019-09-21 12:09:50 +02:00
|
|
|
|
0xfcace3,
|
|
|
|
|
|
0xb3ffff,
|
2019-07-21 11:06:28 +02:00
|
|
|
|
0xffffff,
|
|
|
|
|
|
};
|
|
|
|
|
|
|
2020-07-29 17:27:01 +02:00
|
|
|
|
static const char *const binding_action_map[] = {
|
2020-03-12 10:46:27 +01:00
|
|
|
|
[BIND_ACTION_NONE] = NULL,
|
2020-09-10 18:17:47 +02:00
|
|
|
|
[BIND_ACTION_SCROLLBACK_UP_PAGE] = "scrollback-up-page",
|
|
|
|
|
|
[BIND_ACTION_SCROLLBACK_UP_HALF_PAGE] = "scrollback-up-half-page",
|
|
|
|
|
|
[BIND_ACTION_SCROLLBACK_UP_LINE] = "scrollback-up-line",
|
|
|
|
|
|
[BIND_ACTION_SCROLLBACK_DOWN_PAGE] = "scrollback-down-page",
|
|
|
|
|
|
[BIND_ACTION_SCROLLBACK_DOWN_HALF_PAGE] = "scrollback-down-half-page",
|
|
|
|
|
|
[BIND_ACTION_SCROLLBACK_DOWN_LINE] = "scrollback-down-line",
|
2020-03-09 20:03:04 +01:00
|
|
|
|
[BIND_ACTION_CLIPBOARD_COPY] = "clipboard-copy",
|
|
|
|
|
|
[BIND_ACTION_CLIPBOARD_PASTE] = "clipboard-paste",
|
|
|
|
|
|
[BIND_ACTION_PRIMARY_PASTE] = "primary-paste",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_START] = "search-start",
|
|
|
|
|
|
[BIND_ACTION_FONT_SIZE_UP] = "font-increase",
|
|
|
|
|
|
[BIND_ACTION_FONT_SIZE_DOWN] = "font-decrease",
|
|
|
|
|
|
[BIND_ACTION_FONT_SIZE_RESET] = "font-reset",
|
|
|
|
|
|
[BIND_ACTION_SPAWN_TERMINAL] = "spawn-terminal",
|
2020-03-12 09:34:09 +01:00
|
|
|
|
[BIND_ACTION_MINIMIZE] = "minimize",
|
|
|
|
|
|
[BIND_ACTION_MAXIMIZE] = "maximize",
|
|
|
|
|
|
[BIND_ACTION_FULLSCREEN] = "fullscreen",
|
2020-07-15 09:46:13 +02:00
|
|
|
|
[BIND_ACTION_PIPE_SCROLLBACK] = "pipe-scrollback",
|
|
|
|
|
|
[BIND_ACTION_PIPE_VIEW] = "pipe-visible",
|
2020-07-31 17:02:53 +02:00
|
|
|
|
[BIND_ACTION_PIPE_SELECTED] = "pipe-selected",
|
2021-02-04 20:55:08 +01:00
|
|
|
|
[BIND_ACTION_SHOW_URLS_COPY] = "show-urls-copy",
|
2021-02-04 20:39:13 +01:00
|
|
|
|
[BIND_ACTION_SHOW_URLS_LAUNCH] = "show-urls-launch",
|
2020-08-11 09:55:33 +02:00
|
|
|
|
|
|
|
|
|
|
/* Mouse-specific actions */
|
|
|
|
|
|
[BIND_ACTION_SELECT_BEGIN] = "select-begin",
|
2020-08-11 10:17:19 +02:00
|
|
|
|
[BIND_ACTION_SELECT_BEGIN_BLOCK] = "select-begin-block",
|
|
|
|
|
|
[BIND_ACTION_SELECT_EXTEND] = "select-extend",
|
2021-01-06 11:11:46 +01:00
|
|
|
|
[BIND_ACTION_SELECT_EXTEND_CHAR_WISE] = "select-extend-character-wise",
|
2020-08-11 09:55:33 +02:00
|
|
|
|
[BIND_ACTION_SELECT_WORD] = "select-word",
|
|
|
|
|
|
[BIND_ACTION_SELECT_WORD_WS] = "select-word-whitespace",
|
2020-08-11 10:17:19 +02:00
|
|
|
|
[BIND_ACTION_SELECT_ROW] = "select-row",
|
2020-03-09 20:03:04 +01:00
|
|
|
|
};
|
|
|
|
|
|
|
2020-03-12 09:34:09 +01:00
|
|
|
|
static_assert(ALEN(binding_action_map) == BIND_ACTION_COUNT,
|
|
|
|
|
|
"binding action map size mismatch");
|
|
|
|
|
|
|
2020-08-23 07:44:02 +02:00
|
|
|
|
#define LOG_AND_NOTIFY_ERR(...) \
|
2020-08-10 19:38:53 +02:00
|
|
|
|
do { \
|
2020-08-23 07:44:02 +02:00
|
|
|
|
LOG_ERR(__VA_ARGS__); \
|
|
|
|
|
|
char *text = xasprintf(__VA_ARGS__); \
|
2020-08-10 19:38:53 +02:00
|
|
|
|
struct user_notification notif = { \
|
|
|
|
|
|
.kind = USER_NOTIFICATION_ERROR, \
|
|
|
|
|
|
.text = text, \
|
|
|
|
|
|
}; \
|
|
|
|
|
|
tll_push_back(conf->notifications, notif); \
|
|
|
|
|
|
} while (0)
|
2020-07-31 17:07:14 +02:00
|
|
|
|
|
2020-08-23 07:44:02 +02:00
|
|
|
|
#define LOG_AND_NOTIFY_WARN(...) \
|
2020-08-10 19:38:53 +02:00
|
|
|
|
do { \
|
2020-08-23 07:44:02 +02:00
|
|
|
|
LOG_WARN(__VA_ARGS__); \
|
|
|
|
|
|
char *text = xasprintf(__VA_ARGS__); \
|
2020-07-31 17:07:14 +02:00
|
|
|
|
struct user_notification notif = { \
|
|
|
|
|
|
.kind = USER_NOTIFICATION_WARNING, \
|
|
|
|
|
|
.text = text, \
|
|
|
|
|
|
}; \
|
|
|
|
|
|
tll_push_back(conf->notifications, notif); \
|
2020-08-10 19:38:53 +02:00
|
|
|
|
} while (0)
|
2020-07-31 17:07:14 +02:00
|
|
|
|
|
2020-08-23 07:44:02 +02:00
|
|
|
|
#define LOG_AND_NOTIFY_ERRNO(...) \
|
2020-08-10 19:38:53 +02:00
|
|
|
|
do { \
|
2021-02-21 20:33:07 +01:00
|
|
|
|
int errno_copy = errno; \
|
2020-08-23 07:44:02 +02:00
|
|
|
|
LOG_ERRNO(__VA_ARGS__); \
|
|
|
|
|
|
int len = snprintf(NULL, 0, __VA_ARGS__); \
|
2021-02-21 20:33:07 +01:00
|
|
|
|
int errno_len = snprintf(NULL, 0, ": %s", strerror(errno_copy)); \
|
2020-08-10 19:38:53 +02:00
|
|
|
|
char *text = xmalloc(len + errno_len + 1); \
|
2020-08-23 07:44:02 +02:00
|
|
|
|
snprintf(text, len + errno_len + 1, __VA_ARGS__); \
|
2021-02-21 20:33:07 +01:00
|
|
|
|
snprintf(&text[len], errno_len + 1, ": %s", strerror(errno_copy)); \
|
2020-08-10 19:38:53 +02:00
|
|
|
|
struct user_notification notif = { \
|
|
|
|
|
|
.kind = USER_NOTIFICATION_ERROR, \
|
|
|
|
|
|
.text = text, \
|
|
|
|
|
|
}; \
|
|
|
|
|
|
tll_push_back(conf->notifications, notif); \
|
|
|
|
|
|
} while(0)
|
2020-07-31 17:07:14 +02:00
|
|
|
|
|
2019-07-17 09:29:56 +02:00
|
|
|
|
static char *
|
|
|
|
|
|
get_shell(void)
|
|
|
|
|
|
{
|
2020-03-02 18:45:38 +01:00
|
|
|
|
const char *shell = getenv("SHELL");
|
|
|
|
|
|
|
|
|
|
|
|
if (shell == NULL) {
|
|
|
|
|
|
struct passwd *passwd = getpwuid(getuid());
|
|
|
|
|
|
if (passwd == NULL) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_ERRNO("failed to lookup user: falling back to 'sh'");
|
|
|
|
|
|
shell = "sh";
|
|
|
|
|
|
} else
|
|
|
|
|
|
shell = passwd->pw_shell;
|
2019-07-17 09:29:56 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
LOG_DBG("user's shell: %s", shell);
|
2020-08-04 23:28:16 +01:00
|
|
|
|
return xstrdup(shell);
|
2019-07-17 09:29:56 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
struct config_file {
|
|
|
|
|
|
char *path; /* Full, absolute, path */
|
|
|
|
|
|
int fd; /* FD of file, O_RDONLY */
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
struct path_component {
|
|
|
|
|
|
const char *component;
|
|
|
|
|
|
int fd;
|
|
|
|
|
|
};
|
|
|
|
|
|
typedef tll(struct path_component) path_components_t;
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
|
path_component_add(path_components_t *components, const char *comp, int fd)
|
2019-07-16 11:52:22 +02:00
|
|
|
|
{
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(comp != NULL);
|
|
|
|
|
|
xassert(fd >= 0);
|
2020-08-27 19:48:13 +02:00
|
|
|
|
|
|
|
|
|
|
struct path_component pc = {.component = comp, .fd = fd};
|
|
|
|
|
|
tll_push_back(*components, pc);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
|
path_component_destroy(struct path_component *component)
|
|
|
|
|
|
{
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(component->fd >= 0);
|
2020-08-27 19:48:13 +02:00
|
|
|
|
close(component->fd);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
|
path_components_destroy(path_components_t *components)
|
|
|
|
|
|
{
|
|
|
|
|
|
tll_foreach(*components, it) {
|
|
|
|
|
|
path_component_destroy(&it->item);
|
|
|
|
|
|
tll_remove(*components, it);
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static struct config_file
|
|
|
|
|
|
path_components_to_config_file(const path_components_t *components)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (tll_length(*components) == 0)
|
|
|
|
|
|
goto err;
|
|
|
|
|
|
|
|
|
|
|
|
size_t len = 0;
|
|
|
|
|
|
tll_foreach(*components, it)
|
|
|
|
|
|
len += strlen(it->item.component) + 1;
|
|
|
|
|
|
|
|
|
|
|
|
char *path = malloc(len);
|
|
|
|
|
|
if (path == NULL)
|
|
|
|
|
|
goto err;
|
|
|
|
|
|
|
|
|
|
|
|
size_t idx = 0;
|
|
|
|
|
|
tll_foreach(*components, it) {
|
|
|
|
|
|
strcpy(&path[idx], it->item.component);
|
|
|
|
|
|
idx += strlen(it->item.component);
|
|
|
|
|
|
path[idx++] = '/';
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
2020-08-27 19:48:13 +02:00
|
|
|
|
path[idx - 1] = '\0'; /* Strip last ’/’ */
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
int fd_copy = dup(tll_back(*components).fd);
|
|
|
|
|
|
if (fd_copy < 0) {
|
|
|
|
|
|
free(path);
|
|
|
|
|
|
goto err;
|
|
|
|
|
|
}
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
return (struct config_file){.path = path, .fd = fd_copy};
|
|
|
|
|
|
|
|
|
|
|
|
err:
|
|
|
|
|
|
return (struct config_file){.path = NULL, .fd = -1};
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
static const char *
|
|
|
|
|
|
get_user_home_dir(void)
|
2019-07-16 11:52:22 +02:00
|
|
|
|
{
|
2020-08-27 19:48:13 +02:00
|
|
|
|
const struct passwd *passwd = getpwuid(getuid());
|
|
|
|
|
|
if (passwd == NULL)
|
2019-07-16 11:52:22 +02:00
|
|
|
|
return NULL;
|
2020-08-27 19:48:13 +02:00
|
|
|
|
return passwd->pw_dir;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
try_open_file(path_components_t *components, const char *name)
|
2019-07-16 11:52:22 +02:00
|
|
|
|
{
|
2020-08-27 19:48:13 +02:00
|
|
|
|
int parent_fd = tll_back(*components).fd;
|
|
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
struct stat st;
|
2020-08-27 19:48:13 +02:00
|
|
|
|
if (fstatat(parent_fd, name, &st, 0) == 0 && S_ISREG(st.st_mode)) {
|
|
|
|
|
|
int fd = openat(parent_fd, name, O_RDONLY);
|
|
|
|
|
|
if (fd >= 0) {
|
|
|
|
|
|
path_component_add(components, name, fd);
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static struct config_file
|
2021-03-16 09:54:32 +01:00
|
|
|
|
open_config(void)
|
2020-08-27 19:48:13 +02:00
|
|
|
|
{
|
|
|
|
|
|
struct config_file ret = {.path = NULL, .fd = -1};
|
|
|
|
|
|
|
|
|
|
|
|
path_components_t components = tll_init();
|
|
|
|
|
|
|
|
|
|
|
|
const char *xdg_config_home = getenv("XDG_CONFIG_HOME");
|
|
|
|
|
|
const char *user_home_dir = get_user_home_dir();
|
|
|
|
|
|
char *xdg_config_dirs_copy = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
/* Use XDG_CONFIG_HOME, or ~/.config */
|
|
|
|
|
|
if (xdg_config_home != NULL) {
|
|
|
|
|
|
int fd = open(xdg_config_home, O_RDONLY);
|
|
|
|
|
|
if (fd >= 0)
|
|
|
|
|
|
path_component_add(&components, xdg_config_home, fd);
|
|
|
|
|
|
} else if (user_home_dir != NULL) {
|
|
|
|
|
|
int home_fd = open(user_home_dir, O_RDONLY);
|
|
|
|
|
|
if (home_fd >= 0) {
|
|
|
|
|
|
int config_fd = openat(home_fd, ".config", O_RDONLY);
|
|
|
|
|
|
if (config_fd >= 0) {
|
|
|
|
|
|
path_component_add(&components, user_home_dir, home_fd);
|
|
|
|
|
|
path_component_add(&components, ".config", config_fd);
|
|
|
|
|
|
} else
|
|
|
|
|
|
close(home_fd);
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* First look for foot/foot.ini */
|
|
|
|
|
|
if (tll_length(components) > 0) {
|
|
|
|
|
|
int foot_fd = openat(tll_back(components).fd, "foot", O_RDONLY);
|
|
|
|
|
|
if (foot_fd >= 0) {
|
|
|
|
|
|
path_component_add(&components, "foot", foot_fd);
|
|
|
|
|
|
|
|
|
|
|
|
if (try_open_file(&components, "foot.ini"))
|
|
|
|
|
|
goto done;
|
|
|
|
|
|
|
|
|
|
|
|
struct path_component pc = tll_pop_back(components);
|
|
|
|
|
|
path_component_destroy(&pc);
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* Finally, try foot/foot.ini in all XDG_CONFIG_DIRS */
|
|
|
|
|
|
const char *xdg_config_dirs = getenv("XDG_CONFIG_DIRS");
|
|
|
|
|
|
xdg_config_dirs_copy = xdg_config_dirs != NULL
|
|
|
|
|
|
? strdup(xdg_config_dirs) : NULL;
|
|
|
|
|
|
|
|
|
|
|
|
if (xdg_config_dirs_copy != NULL) {
|
|
|
|
|
|
for (char *save = NULL,
|
|
|
|
|
|
*xdg_dir = strtok_r(xdg_config_dirs_copy, ":", &save);
|
|
|
|
|
|
xdg_dir != NULL;
|
|
|
|
|
|
xdg_dir = strtok_r(NULL, ":", &save))
|
|
|
|
|
|
{
|
|
|
|
|
|
path_components_destroy(&components);
|
|
|
|
|
|
|
|
|
|
|
|
int xdg_fd = open(xdg_dir, O_RDONLY);
|
|
|
|
|
|
if (xdg_fd < 0)
|
|
|
|
|
|
continue;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
int foot_fd = openat(xdg_fd, "foot", O_RDONLY);
|
|
|
|
|
|
if (foot_fd < 0) {
|
|
|
|
|
|
close(xdg_fd);
|
|
|
|
|
|
continue;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(tll_length(components) == 0);
|
2020-08-27 19:48:13 +02:00
|
|
|
|
path_component_add(&components, xdg_dir, xdg_fd);
|
|
|
|
|
|
path_component_add(&components, "foot", foot_fd);
|
|
|
|
|
|
|
|
|
|
|
|
if (try_open_file(&components, "foot.ini"))
|
|
|
|
|
|
goto done;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
out:
|
|
|
|
|
|
path_components_destroy(&components);
|
|
|
|
|
|
free(xdg_config_dirs_copy);
|
|
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
|
|
|
|
done:
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(tll_length(components) > 0);
|
2020-08-27 19:48:13 +02:00
|
|
|
|
ret = path_components_to_config_file(&components);
|
|
|
|
|
|
goto out;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-11 16:10:14 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
str_to_bool(const char *s)
|
|
|
|
|
|
{
|
|
|
|
|
|
return strcasecmp(s, "on") == 0 ||
|
|
|
|
|
|
strcasecmp(s, "true") == 0 ||
|
|
|
|
|
|
strcasecmp(s, "yes") == 0 ||
|
|
|
|
|
|
strtoul(s, NULL, 0) > 0;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-23 18:54:58 +02:00
|
|
|
|
static bool
|
2019-07-29 20:13:26 +02:00
|
|
|
|
str_to_ulong(const char *s, int base, unsigned long *res)
|
2019-07-23 18:54:58 +02:00
|
|
|
|
{
|
|
|
|
|
|
if (s == NULL)
|
|
|
|
|
|
return false;
|
|
|
|
|
|
|
|
|
|
|
|
errno = 0;
|
|
|
|
|
|
char *end = NULL;
|
|
|
|
|
|
|
2019-07-29 20:13:26 +02:00
|
|
|
|
*res = strtoul(s, &end, base);
|
|
|
|
|
|
return errno == 0 && *end == '\0';
|
|
|
|
|
|
}
|
2019-07-23 18:54:58 +02:00
|
|
|
|
|
2019-08-15 18:15:43 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
str_to_double(const char *s, double *res)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (s == NULL)
|
|
|
|
|
|
return false;
|
|
|
|
|
|
|
|
|
|
|
|
errno = 0;
|
|
|
|
|
|
char *end = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
*res = strtod(s, &end);
|
|
|
|
|
|
return errno == 0 && *end == '\0';
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-13 11:42:21 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
str_to_wchars(const char *s, wchar_t **res, struct config *conf,
|
|
|
|
|
|
const char *path, int lineno,
|
|
|
|
|
|
const char *section, const char *key)
|
|
|
|
|
|
{
|
|
|
|
|
|
*res = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
size_t chars = mbstowcs(NULL, s, 0);
|
|
|
|
|
|
if (chars == (size_t)-1) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [%s]: %s: invalid string: %s",
|
|
|
|
|
|
path, lineno, section, key, s);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
*res = xmalloc((chars + 1) * sizeof(wchar_t));
|
|
|
|
|
|
mbstowcs(*res, s, chars + 1);
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-29 20:13:26 +02:00
|
|
|
|
static bool
|
2021-01-07 17:00:13 +01:00
|
|
|
|
str_to_color(const char *s, uint32_t *color, bool allow_alpha,
|
|
|
|
|
|
struct config *conf, const char *path, int lineno,
|
2020-07-31 17:07:14 +02:00
|
|
|
|
const char *section, const char *key)
|
2019-07-29 20:13:26 +02:00
|
|
|
|
{
|
|
|
|
|
|
unsigned long value;
|
|
|
|
|
|
if (!str_to_ulong(s, 16, &value)) {
|
2021-01-07 17:00:13 +01:00
|
|
|
|
LOG_AND_NOTIFY_ERRNO(
|
|
|
|
|
|
"%s:%d: [%s]: %s: invalid color: %s", path, lineno, section, key, s);
|
2019-07-23 18:54:58 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-02 18:42:49 +01:00
|
|
|
|
if (!allow_alpha && (value & 0xff000000) != 0) {
|
2021-01-07 17:00:13 +01:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [%s]: %s: color value must not have an alpha component: %s",
|
|
|
|
|
|
path, lineno, section, key, s);
|
2020-03-02 18:42:49 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
*color = value;
|
2019-07-23 18:54:58 +02:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-06 11:10:40 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
str_to_two_colors(const char *s, uint32_t *first, uint32_t *second,
|
|
|
|
|
|
bool allow_alpha, struct config *conf, const char *path,
|
|
|
|
|
|
int lineno, const char *section, const char *key)
|
|
|
|
|
|
{
|
|
|
|
|
|
/* TODO: do this without strdup() */
|
|
|
|
|
|
char *value_copy = xstrdup(s);
|
|
|
|
|
|
const char *first_as_str = strtok(value_copy, " ");
|
|
|
|
|
|
const char *second_as_str = strtok(NULL, " ");
|
|
|
|
|
|
|
|
|
|
|
|
if (first_as_str == NULL || second_as_str == NULL ||
|
|
|
|
|
|
!str_to_color(first_as_str, first, allow_alpha, conf, path, lineno, section, key) ||
|
|
|
|
|
|
!str_to_color(second_as_str, second, allow_alpha, conf, path, lineno, section, key))
|
|
|
|
|
|
{
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [%s]: %s: invalid colors: %s",
|
|
|
|
|
|
path, lineno, section, key, s);
|
|
|
|
|
|
free(value_copy);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
free(value_copy);
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-07 17:00:58 +01:00
|
|
|
|
static bool
|
2021-01-11 19:37:05 +01:00
|
|
|
|
str_to_pt_or_px(const char *s, struct pt_or_px *res, struct config *conf,
|
2021-01-07 17:00:58 +01:00
|
|
|
|
const char *path, int lineno, const char *section, const char *key)
|
|
|
|
|
|
{
|
|
|
|
|
|
size_t len = s != NULL ? strlen(s) : 0;
|
|
|
|
|
|
if (len >= 2 && s[len - 2] == 'p' && s[len - 1] == 'x') {
|
|
|
|
|
|
errno = 0;
|
|
|
|
|
|
char *end = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
long value = strtol(s, &end, 10);
|
|
|
|
|
|
if (!(errno == 0 && end == s + len - 2)) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [%s]: %s: "
|
|
|
|
|
|
"expected an integer directly followed by 'px', got '%s'",
|
|
|
|
|
|
path, lineno, section, key, s);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
res->pt = 0;
|
|
|
|
|
|
res->px = value;
|
|
|
|
|
|
} else {
|
|
|
|
|
|
double value;
|
|
|
|
|
|
if (!str_to_double(s, &value)) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [%s]: %s: expected a decimal value, got '%s'",
|
|
|
|
|
|
path, lineno, section, key, s);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
res->pt = value;
|
|
|
|
|
|
res->px = 0;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-31 14:27:13 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
str_to_spawn_template(struct config *conf,
|
|
|
|
|
|
const char *s, struct config_spawn_template *template,
|
|
|
|
|
|
const char *path, int lineno, const char *section,
|
|
|
|
|
|
const char *key)
|
|
|
|
|
|
{
|
|
|
|
|
|
free(template->raw_cmd);
|
|
|
|
|
|
free(template->argv);
|
|
|
|
|
|
|
|
|
|
|
|
template->raw_cmd = NULL;
|
|
|
|
|
|
template->argv = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
char *raw_cmd = xstrdup(s);
|
|
|
|
|
|
char **argv = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
if (!tokenize_cmdline(raw_cmd, &argv)) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [%s]: %s: syntax error in command line",
|
|
|
|
|
|
path, lineno, section, key);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
template->raw_cmd = raw_cmd;
|
|
|
|
|
|
template->argv = argv;
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
static bool
|
2019-07-17 10:12:14 +02:00
|
|
|
|
parse_section_main(const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
2019-07-16 11:52:22 +02:00
|
|
|
|
{
|
2019-07-18 14:29:40 +02:00
|
|
|
|
if (strcmp(key, "term") == 0) {
|
|
|
|
|
|
free(conf->term);
|
2020-08-04 23:28:16 +01:00
|
|
|
|
conf->term = xstrdup(value);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-17 09:40:58 +02:00
|
|
|
|
else if (strcmp(key, "shell") == 0) {
|
|
|
|
|
|
free(conf->shell);
|
2020-08-04 23:28:16 +01:00
|
|
|
|
conf->shell = xstrdup(value);
|
2019-07-17 09:40:58 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-02-20 18:35:10 +01:00
|
|
|
|
else if (strcmp(key, "login-shell") == 0) {
|
2020-03-11 16:10:14 +01:00
|
|
|
|
conf->login_shell = str_to_bool(value);
|
2020-02-20 18:35:10 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-04-01 19:59:47 +02:00
|
|
|
|
else if (strcmp(key, "title") == 0) {
|
|
|
|
|
|
free(conf->title);
|
2020-08-04 23:28:16 +01:00
|
|
|
|
conf->title = xstrdup(value);
|
2020-04-01 19:59:47 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-04-01 18:40:51 +02:00
|
|
|
|
else if (strcmp(key, "app-id") == 0) {
|
|
|
|
|
|
free(conf->app_id);
|
2020-08-04 23:28:16 +01:00
|
|
|
|
conf->app_id = xstrdup(value);
|
2020-04-01 18:40:51 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-12-08 19:53:36 +01:00
|
|
|
|
else if (strcmp(key, "initial-window-size-pixels") == 0) {
|
2019-08-23 17:26:41 +02:00
|
|
|
|
unsigned width, height;
|
|
|
|
|
|
if (sscanf(value, "%ux%u", &width, &height) != 2 || width == 0 || height == 0) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
2020-09-08 19:17:29 +02:00
|
|
|
|
"%s: %d: [default]: initial-window-size-pixels: "
|
|
|
|
|
|
"expected WIDTHxHEIGHT, where both are positive integers, "
|
|
|
|
|
|
"got '%s'", path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->size.type = CONF_SIZE_PX;
|
2020-11-30 02:24:38 +00:00
|
|
|
|
conf->size.width = width;
|
|
|
|
|
|
conf->size.height = height;
|
2020-09-08 19:17:29 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "initial-window-size-chars") == 0) {
|
|
|
|
|
|
unsigned width, height;
|
|
|
|
|
|
if (sscanf(value, "%ux%u", &width, &height) != 2 || width == 0 || height == 0) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s: %d: [default]: initial-window-size-chars: "
|
|
|
|
|
|
"expected WIDTHxHEIGHT, where both are positive integers, "
|
|
|
|
|
|
"got '%s'", path, lineno, value);
|
2019-08-23 17:26:41 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-09-08 19:17:29 +02:00
|
|
|
|
conf->size.type = CONF_SIZE_CELLS;
|
2020-11-30 02:24:38 +00:00
|
|
|
|
conf->size.width = width;
|
|
|
|
|
|
conf->size.height = height;
|
2019-08-23 17:26:41 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-02-15 19:00:56 +01:00
|
|
|
|
else if (strcmp(key, "pad") == 0) {
|
|
|
|
|
|
unsigned x, y;
|
2021-01-06 11:17:29 +01:00
|
|
|
|
char mode[16] = {0};
|
|
|
|
|
|
|
|
|
|
|
|
int ret = sscanf(value, "%ux%u %15s", &x, &y, mode);
|
|
|
|
|
|
bool center = strcasecmp(mode, "center") == 0;
|
|
|
|
|
|
bool invalid_mode = !center && mode[0] != '\0';
|
|
|
|
|
|
|
|
|
|
|
|
if ((ret != 2 && ret != 3) || invalid_mode) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
2021-01-06 11:17:29 +01:00
|
|
|
|
"%s:%d: [default]: pad: expected PAD_XxPAD_Y [center], "
|
2020-07-31 17:07:14 +02:00
|
|
|
|
"where both are positive integers, got '%s'",
|
2020-02-15 19:00:56 +01:00
|
|
|
|
path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->pad_x = x;
|
|
|
|
|
|
conf->pad_y = y;
|
2021-01-06 11:17:29 +01:00
|
|
|
|
conf->center = center;
|
2020-02-15 19:00:56 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-21 15:14:43 +01:00
|
|
|
|
else if (strcmp(key, "resize-delay-ms") == 0) {
|
|
|
|
|
|
unsigned long ms;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &ms)) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [default]: resize-delay-ms: "
|
|
|
|
|
|
"expected an integer, got '%s'",
|
|
|
|
|
|
path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->resize_delay_ms = ms;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-04-17 21:57:08 +02:00
|
|
|
|
else if (strcmp(key, "bold-text-in-bright") == 0) {
|
|
|
|
|
|
if (strcmp(value, "palette-based") == 0) {
|
|
|
|
|
|
conf->bold_in_bright.enabled = true;
|
|
|
|
|
|
conf->bold_in_bright.palette_based = true;
|
|
|
|
|
|
} else {
|
|
|
|
|
|
conf->bold_in_bright.enabled = str_to_bool(value);
|
|
|
|
|
|
conf->bold_in_bright.palette_based = false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
2020-11-14 11:21:51 +01:00
|
|
|
|
|
2020-10-08 19:55:32 +02:00
|
|
|
|
else if (strcmp(key, "bell") == 0) {
|
|
|
|
|
|
if (strcmp(value, "set-urgency") == 0)
|
2020-12-10 18:22:48 +01:00
|
|
|
|
conf->bell_action = BELL_ACTION_URGENT;
|
|
|
|
|
|
else if (strcmp(value, "notify") == 0)
|
|
|
|
|
|
conf->bell_action = BELL_ACTION_NOTIFY;
|
2020-10-08 19:55:32 +02:00
|
|
|
|
else if (strcmp(value, "none") == 0)
|
2020-12-10 18:22:48 +01:00
|
|
|
|
conf->bell_action = BELL_ACTION_NONE;
|
2020-10-08 19:55:32 +02:00
|
|
|
|
else {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [default]: bell: "
|
2020-12-10 18:22:48 +01:00
|
|
|
|
"expected either 'set-urgency', 'notify' or 'none'",
|
|
|
|
|
|
path, lineno);
|
|
|
|
|
|
conf->bell_action = BELL_ACTION_NONE;
|
2020-10-08 19:55:32 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-28 12:04:00 +01:00
|
|
|
|
else if (strcmp(key, "initial-window-mode") == 0) {
|
2020-03-26 19:39:12 +01:00
|
|
|
|
if (strcmp(value, "windowed") == 0)
|
|
|
|
|
|
conf->startup_mode = STARTUP_WINDOWED;
|
|
|
|
|
|
else if (strcmp(value, "maximized") == 0)
|
|
|
|
|
|
conf->startup_mode = STARTUP_MAXIMIZED;
|
|
|
|
|
|
else if (strcmp(value, "fullscreen") == 0)
|
|
|
|
|
|
conf->startup_mode = STARTUP_FULLSCREEN;
|
|
|
|
|
|
else {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [default]: initial-window-mode: expected either "
|
|
|
|
|
|
"'windowed', 'maximized' or 'fullscreen'",
|
2020-03-26 19:39:12 +01:00
|
|
|
|
path, lineno);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-10-20 21:04:47 +02:00
|
|
|
|
else if (strcmp(key, "font") == 0 ||
|
|
|
|
|
|
strcmp(key, "font-bold") == 0 ||
|
|
|
|
|
|
strcmp(key, "font-italic") == 0 ||
|
|
|
|
|
|
strcmp(key, "font-bold-italic") == 0)
|
|
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
|
size_t idx =
|
|
|
|
|
|
strcmp(key, "font") == 0 ? 0 :
|
|
|
|
|
|
strcmp(key, "font-bold") == 0 ? 1 :
|
|
|
|
|
|
strcmp(key, "font-italic") == 0 ? 2 : 3;
|
|
|
|
|
|
|
|
|
|
|
|
tll_foreach(conf->fonts[idx], it)
|
|
|
|
|
|
config_font_destroy(&it->item);
|
|
|
|
|
|
tll_free(conf->fonts[idx]);
|
|
|
|
|
|
|
2020-08-04 23:28:16 +01:00
|
|
|
|
char *copy = xstrdup(value);
|
2019-12-05 19:33:54 +01:00
|
|
|
|
for (const char *font = strtok(copy, ","); font != NULL; font = strtok(NULL, ",")) {
|
|
|
|
|
|
/* Trim spaces, strictly speaking not necessary, but looks nice :) */
|
|
|
|
|
|
while (*font != '\0' && isspace(*font))
|
|
|
|
|
|
font++;
|
2020-12-15 18:55:27 +01:00
|
|
|
|
if (*font != '\0') {
|
|
|
|
|
|
struct config_font font_data;
|
|
|
|
|
|
if (!config_font_parse(font, &font_data)) {
|
|
|
|
|
|
LOG_ERR("%s:%d: [default]: %s: invalid font specification",
|
|
|
|
|
|
path, lineno, key);
|
|
|
|
|
|
free(copy);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
tll_push_back(conf->fonts[idx], font_data);
|
|
|
|
|
|
}
|
2019-12-05 19:33:54 +01:00
|
|
|
|
}
|
2019-07-30 18:04:28 +02:00
|
|
|
|
free(copy);
|
2019-07-18 14:29:40 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-07 11:16:02 +01:00
|
|
|
|
else if (strcmp(key, "line-height") == 0) {
|
2021-01-07 17:00:58 +01:00
|
|
|
|
if (!str_to_pt_or_px(value, &conf->line_height,
|
|
|
|
|
|
conf, path, lineno, "default", "line-height"))
|
2021-01-07 11:16:02 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "letter-spacing") == 0) {
|
2021-01-07 17:00:58 +01:00
|
|
|
|
if (!str_to_pt_or_px(value, &conf->letter_spacing,
|
|
|
|
|
|
conf, path, lineno, "default", "letter-spacing"))
|
2021-01-07 11:16:02 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "horizontal-letter-offset") == 0) {
|
2021-01-07 17:00:58 +01:00
|
|
|
|
if (!str_to_pt_or_px(
|
|
|
|
|
|
value, &conf->horizontal_letter_offset,
|
|
|
|
|
|
conf, path, lineno, "default", "horizontal-letter-offset"))
|
2021-01-07 11:16:02 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "vertical-letter-offset") == 0) {
|
2021-01-07 17:00:58 +01:00
|
|
|
|
if (!str_to_pt_or_px(
|
2021-03-01 13:44:46 +01:00
|
|
|
|
value, &conf->vertical_letter_offset,
|
2021-01-07 17:00:58 +01:00
|
|
|
|
conf, path, lineno, "default", "vertical-letter-offset"))
|
2021-01-07 11:16:02 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-12-17 12:05:22 +01:00
|
|
|
|
else if (strcmp(key, "dpi-aware") == 0) {
|
|
|
|
|
|
if (strcmp(value, "auto") == 0)
|
|
|
|
|
|
conf->dpi_aware = DPI_AWARE_AUTO;
|
|
|
|
|
|
else
|
|
|
|
|
|
conf->dpi_aware = str_to_bool(value) ? DPI_AWARE_YES : DPI_AWARE_NO;
|
|
|
|
|
|
}
|
2020-11-17 17:59:31 +01:00
|
|
|
|
|
2019-07-29 20:13:26 +02:00
|
|
|
|
else if (strcmp(key, "workers") == 0) {
|
|
|
|
|
|
unsigned long count;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &count)) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [default]: workers: expected an integer, got '%s'",
|
|
|
|
|
|
path, lineno, value);
|
2019-07-29 20:13:26 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
conf->render_worker_count = count;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-10-09 19:44:23 +02:00
|
|
|
|
else if (strcmp(key, "word-delimiters") == 0) {
|
2021-02-13 11:42:21 +01:00
|
|
|
|
wchar_t *word_delimiters;
|
|
|
|
|
|
if (!str_to_wchars(value, &word_delimiters, conf, path, lineno,
|
|
|
|
|
|
"default", "word-delimiters"))
|
|
|
|
|
|
{
|
2020-10-09 19:44:23 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
free(conf->word_delimiters);
|
2021-02-13 11:42:21 +01:00
|
|
|
|
conf->word_delimiters = word_delimiters;
|
2021-02-13 11:42:40 +01:00
|
|
|
|
}
|
2020-10-09 19:44:23 +02:00
|
|
|
|
|
2021-02-13 11:42:40 +01:00
|
|
|
|
else if (strcmp(key, "jump-label-letters") == 0) {
|
|
|
|
|
|
wchar_t *letters;
|
|
|
|
|
|
if (!str_to_wchars(value, &letters, conf, path, lineno,
|
|
|
|
|
|
"default", "jump-label-letters"))
|
|
|
|
|
|
{
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
free(conf->jump_label_letters);
|
|
|
|
|
|
conf->jump_label_letters = letters;
|
2020-10-09 19:44:23 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-12-08 19:19:55 +01:00
|
|
|
|
else if (strcmp(key, "notify") == 0) {
|
2021-01-31 14:27:13 +01:00
|
|
|
|
if (!str_to_spawn_template(conf, value, &conf->notify, path, lineno,
|
|
|
|
|
|
"default", "notify"))
|
|
|
|
|
|
{
|
2020-12-08 19:19:55 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
2021-01-31 14:27:13 +01:00
|
|
|
|
}
|
2020-12-08 19:19:55 +01:00
|
|
|
|
|
2021-01-31 14:27:13 +01:00
|
|
|
|
else if (strcmp(key, "url-launch") == 0) {
|
|
|
|
|
|
if (!str_to_spawn_template(conf, value, &conf->url_launch, path, lineno,
|
|
|
|
|
|
"default", "url-launch"))
|
|
|
|
|
|
{
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
2020-12-08 19:19:55 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-16 11:26:03 +01:00
|
|
|
|
else if (strcmp(key, "selection-target") == 0) {
|
2021-01-20 17:57:44 +01:00
|
|
|
|
static const char values[][12] = {
|
2021-01-16 15:39:44 +01:00
|
|
|
|
[SELECTION_TARGET_NONE] = "none",
|
|
|
|
|
|
[SELECTION_TARGET_PRIMARY] = "primary",
|
|
|
|
|
|
[SELECTION_TARGET_CLIPBOARD] = "clipboard",
|
|
|
|
|
|
[SELECTION_TARGET_BOTH] = "both",
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
for (size_t i = 0; i < ALEN(values); i++) {
|
|
|
|
|
|
if (strcasecmp(value, values[i]) == 0) {
|
|
|
|
|
|
conf->selection_target = i;
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
2021-01-16 11:26:03 +01:00
|
|
|
|
}
|
2021-01-16 15:39:44 +01:00
|
|
|
|
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [default]: %s: invalid 'selection-target'; "
|
|
|
|
|
|
"must be one of 'none', 'primary', 'clipboard' or 'both",
|
|
|
|
|
|
path, lineno, value);
|
|
|
|
|
|
return false;
|
2021-01-16 11:26:03 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-14 21:29:22 +01:00
|
|
|
|
else if (strcmp(key, "osc8-underline") == 0) {
|
|
|
|
|
|
if (strcmp(value, "url-mode") == 0)
|
|
|
|
|
|
conf->osc8_underline = OSC8_UNDERLINE_URL_MODE;
|
|
|
|
|
|
else if (strcmp(value, "always") == 0)
|
2021-02-19 08:44:38 +01:00
|
|
|
|
conf->osc8_underline = OSC8_UNDERLINE_ALWAYS;
|
2021-02-14 21:29:22 +01:00
|
|
|
|
else {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%u: [default]: %s: invalid 'osc8-underline'; "
|
|
|
|
|
|
"must be one of 'url-mode', or 'always'", path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-04-09 23:19:20 +02:00
|
|
|
|
else if (strcmp(key, "box-drawings-uses-font-glyphs") == 0)
|
|
|
|
|
|
conf->box_drawings_uses_font_glyphs = str_to_bool(value);
|
|
|
|
|
|
|
2020-07-29 17:41:24 +02:00
|
|
|
|
else {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%u: [default]: %s: invalid key", path, lineno, key);
|
2020-07-29 17:41:24 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_scrollback(const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (strcmp(key, "lines") == 0) {
|
2019-08-01 19:28:14 +02:00
|
|
|
|
unsigned long lines;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &lines)) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [scrollback]: lines: expected an integer, got '%s'", path, lineno, value);
|
2019-08-01 19:28:14 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
2020-07-25 14:31:45 +02:00
|
|
|
|
conf->scrollback.lines = lines;
|
2019-08-01 19:28:14 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-07-29 17:41:24 +02:00
|
|
|
|
else if (strcmp(key, "indicator-position") == 0) {
|
2020-07-25 14:31:45 +02:00
|
|
|
|
if (strcmp(value, "none") == 0)
|
2020-07-27 20:02:51 +02:00
|
|
|
|
conf->scrollback.indicator.position = SCROLLBACK_INDICATOR_POSITION_NONE;
|
2020-07-25 14:40:46 +02:00
|
|
|
|
else if (strcmp(value, "fixed") == 0)
|
2020-07-27 20:02:51 +02:00
|
|
|
|
conf->scrollback.indicator.position = SCROLLBACK_INDICATOR_POSITION_FIXED;
|
2020-07-25 14:40:46 +02:00
|
|
|
|
else if (strcmp(value, "relative") == 0)
|
2020-07-27 20:02:51 +02:00
|
|
|
|
conf->scrollback.indicator.position = SCROLLBACK_INDICATOR_POSITION_RELATIVE;
|
2020-07-25 14:31:45 +02:00
|
|
|
|
else {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [scrollback]: indicator-position must be one of "
|
2020-08-23 18:50:11 +02:00
|
|
|
|
"'none', 'fixed' or 'relative'",
|
2020-07-25 14:31:45 +02:00
|
|
|
|
path, lineno);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
2020-07-24 18:20:26 +02:00
|
|
|
|
|
2020-07-29 17:41:24 +02:00
|
|
|
|
else if (strcmp(key, "indicator-format") == 0) {
|
2020-07-28 19:57:26 +02:00
|
|
|
|
if (strcmp(value, "percentage") == 0) {
|
2020-07-26 11:39:02 +02:00
|
|
|
|
conf->scrollback.indicator.format
|
|
|
|
|
|
= SCROLLBACK_INDICATOR_FORMAT_PERCENTAGE;
|
|
|
|
|
|
} else if (strcmp(value, "line") == 0) {
|
|
|
|
|
|
conf->scrollback.indicator.format
|
|
|
|
|
|
= SCROLLBACK_INDICATOR_FORMAT_LINENO;
|
|
|
|
|
|
} else {
|
2020-07-28 19:56:53 +02:00
|
|
|
|
free(conf->scrollback.indicator.text);
|
|
|
|
|
|
conf->scrollback.indicator.text = NULL;
|
|
|
|
|
|
|
2020-08-22 10:56:53 +02:00
|
|
|
|
size_t len = mbstowcs(NULL, value, 0);
|
2020-08-25 19:39:17 +01:00
|
|
|
|
if (len == (size_t)-1) {
|
2020-08-22 10:56:53 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERRNO(
|
|
|
|
|
|
"%s:%d: [scrollback]: indicator-format: "
|
|
|
|
|
|
"invalid value: %s", path, lineno, value);
|
2020-07-28 19:56:53 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-04 23:28:16 +01:00
|
|
|
|
conf->scrollback.indicator.text = xcalloc(len + 1, sizeof(wchar_t));
|
2020-10-09 19:44:23 +02:00
|
|
|
|
mbstowcs(conf->scrollback.indicator.text, value, len + 1);
|
2020-07-24 18:34:19 +02:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-03 19:43:06 +02:00
|
|
|
|
else if (strcmp(key, "multiplier") == 0) {
|
|
|
|
|
|
double multiplier;
|
|
|
|
|
|
if (!str_to_double(value, &multiplier)) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [scrollback]: multiplier: "
|
|
|
|
|
|
"invalid value: %s", path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->scrollback.multiplier = multiplier;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
else {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%u: [scrollback]: %s: invalid key", path, lineno, key);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-21 11:31:16 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_colors(const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
uint32_t *color = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
if (strcmp(key, "foreground") == 0) color = &conf->colors.fg;
|
|
|
|
|
|
else if (strcmp(key, "background") == 0) color = &conf->colors.bg;
|
2021-04-07 08:07:43 +02:00
|
|
|
|
else if (strcmp(key, "regular0") == 0) color = &conf->colors.table[0];
|
|
|
|
|
|
else if (strcmp(key, "regular1") == 0) color = &conf->colors.table[1];
|
|
|
|
|
|
else if (strcmp(key, "regular2") == 0) color = &conf->colors.table[2];
|
|
|
|
|
|
else if (strcmp(key, "regular3") == 0) color = &conf->colors.table[3];
|
|
|
|
|
|
else if (strcmp(key, "regular4") == 0) color = &conf->colors.table[4];
|
|
|
|
|
|
else if (strcmp(key, "regular5") == 0) color = &conf->colors.table[5];
|
|
|
|
|
|
else if (strcmp(key, "regular6") == 0) color = &conf->colors.table[6];
|
|
|
|
|
|
else if (strcmp(key, "regular7") == 0) color = &conf->colors.table[7];
|
|
|
|
|
|
else if (strcmp(key, "bright0") == 0) color = &conf->colors.table[8 + 0];
|
|
|
|
|
|
else if (strcmp(key, "bright1") == 0) color = &conf->colors.table[8 + 1];
|
|
|
|
|
|
else if (strcmp(key, "bright2") == 0) color = &conf->colors.table[8 + 2];
|
|
|
|
|
|
else if (strcmp(key, "bright3") == 0) color = &conf->colors.table[8 + 3];
|
|
|
|
|
|
else if (strcmp(key, "bright4") == 0) color = &conf->colors.table[8 + 4];
|
|
|
|
|
|
else if (strcmp(key, "bright5") == 0) color = &conf->colors.table[8 + 5];
|
|
|
|
|
|
else if (strcmp(key, "bright6") == 0) color = &conf->colors.table[8 + 6];
|
|
|
|
|
|
else if (strcmp(key, "bright7") == 0) color = &conf->colors.table[8 + 7];
|
2020-08-12 18:53:32 +02:00
|
|
|
|
else if (strcmp(key, "selection-foreground") == 0) color = &conf->colors.selection_fg;
|
|
|
|
|
|
else if (strcmp(key, "selection-background") == 0) color = &conf->colors.selection_bg;
|
2021-02-06 11:10:40 +01:00
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "jump-labels") == 0) {
|
|
|
|
|
|
if (!str_to_two_colors(
|
|
|
|
|
|
value, &conf->colors.jump_label.fg, &conf->colors.jump_label.bg,
|
|
|
|
|
|
false, conf, path, lineno, "colors", "jump-labels"))
|
|
|
|
|
|
{
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->colors.use_custom.jump_label = true;
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "urls") == 0) {
|
|
|
|
|
|
if (!str_to_color(value, &conf->colors.url, false,
|
|
|
|
|
|
conf, path, lineno, "colors", "urls"))
|
|
|
|
|
|
{
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->colors.use_custom.url = true;
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-08-15 18:15:43 +02:00
|
|
|
|
else if (strcmp(key, "alpha") == 0) {
|
|
|
|
|
|
double alpha;
|
|
|
|
|
|
if (!str_to_double(value, &alpha) || alpha < 0. || alpha > 1.) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s: %d: [colors]: alpha: expected a value in the range 0.0-1.0",
|
2019-08-15 18:15:43 +02:00
|
|
|
|
path, lineno);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-08-16 22:06:06 +02:00
|
|
|
|
conf->colors.alpha = alpha * 65535.;
|
2019-08-15 18:15:43 +02:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
2019-07-21 11:31:16 +02:00
|
|
|
|
|
|
|
|
|
|
else {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [colors]: %s: invalid key", path, lineno, key);
|
2019-07-21 11:31:16 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-23 18:54:58 +02:00
|
|
|
|
uint32_t color_value;
|
2021-01-07 17:00:13 +01:00
|
|
|
|
if (!str_to_color(value, &color_value, false, conf, path, lineno, "colors", key))
|
2019-07-21 11:31:16 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
|
2019-07-23 18:54:58 +02:00
|
|
|
|
*color = color_value;
|
2019-07-21 11:31:16 +02:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-22 20:15:14 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_cursor(const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (strcmp(key, "style") == 0) {
|
|
|
|
|
|
if (strcmp(value, "block") == 0)
|
|
|
|
|
|
conf->cursor.style = CURSOR_BLOCK;
|
2021-04-30 20:31:47 +02:00
|
|
|
|
else if (strcmp(value, "beam") == 0 || strcmp(value, "bar") == 0)
|
|
|
|
|
|
conf->cursor.style = CURSOR_BEAM;
|
2019-07-22 20:15:14 +02:00
|
|
|
|
else if (strcmp(value, "underline") == 0)
|
|
|
|
|
|
conf->cursor.style = CURSOR_UNDERLINE;
|
|
|
|
|
|
|
|
|
|
|
|
else {
|
2021-04-30 20:31:47 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: style: one of block, beam or underline",
|
|
|
|
|
|
path, lineno);
|
2019-07-22 20:15:14 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-06-30 17:45:34 +02:00
|
|
|
|
else if (strcmp(key, "blink") == 0)
|
|
|
|
|
|
conf->cursor.blink = str_to_bool(value);
|
|
|
|
|
|
|
2019-07-23 18:54:58 +02:00
|
|
|
|
else if (strcmp(key, "color") == 0) {
|
2021-02-06 11:10:40 +01:00
|
|
|
|
if (!str_to_two_colors(
|
|
|
|
|
|
value, &conf->cursor.color.text, &conf->cursor.color.cursor,
|
|
|
|
|
|
false, conf, path, lineno, "cursor", "color"))
|
2019-07-23 18:54:58 +02:00
|
|
|
|
{
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-06 11:10:40 +01:00
|
|
|
|
conf->cursor.color.text |= 1u << 31;
|
|
|
|
|
|
conf->cursor.color.cursor |= 1u << 31;
|
2019-07-23 18:54:58 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-04-30 20:31:47 +02:00
|
|
|
|
else if (strcmp(key, "beam-thickness") == 0) {
|
|
|
|
|
|
if (!str_to_pt_or_px(
|
|
|
|
|
|
value, &conf->cursor.beam_thickness,
|
|
|
|
|
|
conf, path, lineno, "cursor", "beam-thickness"))
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-22 20:15:14 +02:00
|
|
|
|
else {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [cursor]: %s: invalid key", path, lineno, key);
|
2019-07-22 20:15:14 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-04 07:33:15 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_mouse(const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (strcmp(key, "hide-when-typing") == 0)
|
|
|
|
|
|
conf->mouse.hide_when_typing = str_to_bool(value);
|
|
|
|
|
|
|
2020-09-15 19:09:00 +02:00
|
|
|
|
else if (strcmp(key, "alternate-scroll-mode") == 0)
|
|
|
|
|
|
conf->mouse.alternate_scroll_mode = str_to_bool(value);
|
|
|
|
|
|
|
2020-08-04 07:33:15 +02:00
|
|
|
|
else {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: [mouse]: %s: invalid key", path, lineno, key);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-02 18:42:49 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_csd(const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (strcmp(key, "preferred") == 0) {
|
|
|
|
|
|
if (strcmp(value, "server") == 0)
|
|
|
|
|
|
conf->csd.preferred = CONF_CSD_PREFER_SERVER;
|
|
|
|
|
|
else if (strcmp(value, "client") == 0)
|
|
|
|
|
|
conf->csd.preferred = CONF_CSD_PREFER_CLIENT;
|
2020-10-10 11:04:17 +02:00
|
|
|
|
else if (strcmp(value, "none") == 0)
|
|
|
|
|
|
conf->csd.preferred = CONF_CSD_PREFER_NONE;
|
2020-03-02 18:42:49 +01:00
|
|
|
|
else {
|
2020-10-10 11:04:17 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: csd.preferred: expected either "
|
|
|
|
|
|
"'server', 'client' or 'none'", path, lineno);
|
2020-03-02 18:42:49 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-03 18:18:59 +01:00
|
|
|
|
else if (strcmp(key, "color") == 0) {
|
2020-03-02 18:42:49 +01:00
|
|
|
|
uint32_t color;
|
2021-01-07 17:00:13 +01:00
|
|
|
|
if (!str_to_color(value, &color, true, conf, path, lineno, "csd", "color")) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: invalid titlebar-color: %s", path, lineno, value);
|
2020-03-02 18:42:49 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->csd.color.title_set = true;
|
|
|
|
|
|
conf->csd.color.title = color;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-03 18:18:59 +01:00
|
|
|
|
else if (strcmp(key, "size") == 0) {
|
2020-03-02 18:42:49 +01:00
|
|
|
|
unsigned long pixels;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &pixels)) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: expected an integer, got '%s'", path, lineno, value);
|
2020-03-02 18:42:49 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->csd.title_height = pixels;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-02 20:29:28 +01:00
|
|
|
|
else if (strcmp(key, "button-width") == 0) {
|
|
|
|
|
|
unsigned long pixels;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &pixels)) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: expected an integer, got '%s'", path, lineno, value);
|
2020-03-02 20:29:28 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->csd.button_width = pixels;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "button-minimize-color") == 0) {
|
|
|
|
|
|
uint32_t color;
|
2021-01-07 17:00:13 +01:00
|
|
|
|
if (!str_to_color(value, &color, true, conf, path, lineno, "csd", "button-minimize-color")) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: invalid button-minimize-color: %s", path, lineno, value);
|
2020-03-02 20:29:28 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->csd.color.minimize_set = true;
|
|
|
|
|
|
conf->csd.color.minimize = color;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "button-maximize-color") == 0) {
|
|
|
|
|
|
uint32_t color;
|
2021-01-07 17:00:13 +01:00
|
|
|
|
if (!str_to_color(value, &color, true, conf, path, lineno, "csd", "button-maximize-color")) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: invalid button-maximize-color: %s", path, lineno, value);
|
2020-03-02 20:29:28 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->csd.color.maximize_set = true;
|
|
|
|
|
|
conf->csd.color.maximize = color;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "button-close-color") == 0) {
|
|
|
|
|
|
uint32_t color;
|
2021-01-07 17:00:13 +01:00
|
|
|
|
if (!str_to_color(value, &color, true, conf, path, lineno, "csd", "button-close-color")) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: invalid button-close-color: %s", path, lineno, value);
|
2020-03-02 20:29:28 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->csd.color.close_set = true;
|
|
|
|
|
|
conf->csd.color.close = color;
|
|
|
|
|
|
}
|
2020-03-08 14:08:48 +01:00
|
|
|
|
|
|
|
|
|
|
else {
|
2020-08-11 09:55:33 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%u: [csd]: %s: invalid action",
|
|
|
|
|
|
path, lineno, key);
|
2020-03-08 14:08:48 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-02 18:42:49 +01:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Struct that holds temporary key/mouse binding parsed data */
|
|
|
|
|
|
struct key_combo {
|
|
|
|
|
|
char *text; /* Raw text, e.g. "Control+Shift+V" */
|
|
|
|
|
|
struct config_key_modifiers modifiers;
|
|
|
|
|
|
union {
|
|
|
|
|
|
xkb_keysym_t sym; /* Key converted to an XKB symbol, e.g. XKB_KEY_V */
|
|
|
|
|
|
struct {
|
|
|
|
|
|
int button;
|
|
|
|
|
|
int count;
|
|
|
|
|
|
} m;
|
|
|
|
|
|
};
|
|
|
|
|
|
};
|
|
|
|
|
|
typedef tll(struct key_combo) key_combo_list_t;
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
|
free_key_combo_list(key_combo_list_t *key_combos)
|
|
|
|
|
|
{
|
|
|
|
|
|
tll_foreach(*key_combos, it)
|
|
|
|
|
|
free(it->item.text);
|
|
|
|
|
|
tll_free(*key_combos);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-12 17:16:35 +01:00
|
|
|
|
static bool
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
parse_modifiers(struct config *conf, const char *text, size_t len,
|
|
|
|
|
|
struct config_key_modifiers *modifiers, const char *path, unsigned lineno)
|
2020-03-12 17:16:35 +01:00
|
|
|
|
{
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
bool ret = false;
|
2020-03-12 17:16:35 +01:00
|
|
|
|
|
2020-08-23 07:42:20 +02:00
|
|
|
|
*modifiers = (struct config_key_modifiers){0};
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
char *copy = xstrndup(text, len);
|
2020-07-30 18:57:21 +02:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
for (char *tok_ctx = NULL, *key = strtok_r(copy, "+", &tok_ctx);
|
|
|
|
|
|
key != NULL;
|
|
|
|
|
|
key = strtok_r(NULL, "+", &tok_ctx))
|
|
|
|
|
|
{
|
|
|
|
|
|
if (strcmp(key, XKB_MOD_NAME_SHIFT) == 0)
|
|
|
|
|
|
modifiers->shift = true;
|
|
|
|
|
|
else if (strcmp(key, XKB_MOD_NAME_CTRL) == 0)
|
|
|
|
|
|
modifiers->ctrl = true;
|
|
|
|
|
|
else if (strcmp(key, XKB_MOD_NAME_ALT) == 0)
|
|
|
|
|
|
modifiers->alt = true;
|
|
|
|
|
|
else if (strcmp(key, XKB_MOD_NAME_LOGO) == 0)
|
|
|
|
|
|
modifiers->meta = true;
|
|
|
|
|
|
else {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: %s: not a valid modifier name",
|
|
|
|
|
|
path, lineno, key);
|
|
|
|
|
|
goto out;
|
|
|
|
|
|
}
|
2020-07-30 18:57:21 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
ret = true;
|
2020-07-30 18:57:21 +02:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
out:
|
|
|
|
|
|
free(copy);
|
|
|
|
|
|
return ret;
|
|
|
|
|
|
}
|
2020-03-12 17:16:35 +01:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_key_combos(struct config *conf, const char *combos, key_combo_list_t *key_combos,
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
const char *section, const char *option,
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(tll_length(*key_combos) == 0);
|
2020-03-12 17:16:35 +01:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
char *copy = xstrdup(combos);
|
2020-03-12 17:16:35 +01:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
for (char *tok_ctx = NULL, *combo = strtok_r(copy, " ", &tok_ctx);
|
|
|
|
|
|
combo != NULL;
|
|
|
|
|
|
combo = strtok_r(NULL, " ", &tok_ctx))
|
|
|
|
|
|
{
|
2020-08-23 07:42:20 +02:00
|
|
|
|
struct config_key_modifiers modifiers = {0};
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
char *key = strrchr(combo, '+');
|
2020-03-12 17:16:35 +01:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
if (key == NULL) {
|
|
|
|
|
|
/* No modifiers */
|
|
|
|
|
|
key = combo;
|
|
|
|
|
|
} else {
|
|
|
|
|
|
if (!parse_modifiers(conf, combo, key - combo, &modifiers, path, lineno))
|
|
|
|
|
|
goto err;
|
|
|
|
|
|
key++; /* Skip past the '+' */
|
|
|
|
|
|
}
|
2020-03-12 17:16:35 +01:00
|
|
|
|
|
input: repair key combos containing both explicit modifier and shifted symbol
If a user-provided key combo contains both an explicit modifier, and
the shifted symbol it produces, replace the symbol with its un-shifted
version.
Example: Control+Shift+U contains both ‘Shift’, and ‘U’, where ‘Shift’
is the modifier that shifts ‘u’ to ‘U’.
Such modifiers are “consumed”, i.e. filtered out, when matching key
combos. As such, Control+Shift+U will never trigger since we’ll never
be able to match the consumed modifier ‘Shift’.
The above combo can be written in two ways:
- Control+U
- Control+Shift+u
To be able to detect that Control+Shift+U is an invalid combination,
we need to check all *shifted* symbols for all key *codes*.
Once we’ve detected a shifted symbol (and where it differs from the
un-shifted symbol), we loop all modifier sets that produce the shift
level where our shifted symbol is. For each such set, check if it
intersects with the user-provided key combo’s modifier set.
If there is an intersection, it means the user provided a key combo
containing a modifier and symbol, such that the modifier is consumed
when the symbol is produced.
In this case, we replace the symbol with its un-shifted version.
2021-03-02 17:50:06 +01:00
|
|
|
|
#if 0
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
if (modifiers.shift && strlen(key) == 1 && (*key >= 'A' && *key <= 'Z')) {
|
|
|
|
|
|
LOG_WARN(
|
|
|
|
|
|
"%s:%d: [%s]: %s: %s: "
|
|
|
|
|
|
"upper case keys not supported with explicit 'Shift' modifier",
|
|
|
|
|
|
path, lineno, section, option, combo);
|
|
|
|
|
|
user_notification_add(
|
|
|
|
|
|
&conf->notifications, USER_NOTIFICATION_DEPRECATED,
|
|
|
|
|
|
"%s:%d: [%s]: %s: \033[1m%s\033[m: "
|
|
|
|
|
|
"shifted keys not supported with explicit \033[1mShift\033[m "
|
|
|
|
|
|
"modifier",
|
|
|
|
|
|
path, lineno, section, option, combo);
|
2021-02-28 11:38:33 +01:00
|
|
|
|
*key = *key - 'A' + 'a';
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
}
|
input: repair key combos containing both explicit modifier and shifted symbol
If a user-provided key combo contains both an explicit modifier, and
the shifted symbol it produces, replace the symbol with its un-shifted
version.
Example: Control+Shift+U contains both ‘Shift’, and ‘U’, where ‘Shift’
is the modifier that shifts ‘u’ to ‘U’.
Such modifiers are “consumed”, i.e. filtered out, when matching key
combos. As such, Control+Shift+U will never trigger since we’ll never
be able to match the consumed modifier ‘Shift’.
The above combo can be written in two ways:
- Control+U
- Control+Shift+u
To be able to detect that Control+Shift+U is an invalid combination,
we need to check all *shifted* symbols for all key *codes*.
Once we’ve detected a shifted symbol (and where it differs from the
un-shifted symbol), we loop all modifier sets that produce the shift
level where our shifted symbol is. For each such set, check if it
intersects with the user-provided key combo’s modifier set.
If there is an intersection, it means the user provided a key combo
containing a modifier and symbol, such that the modifier is consumed
when the symbol is produced.
In this case, we replace the symbol with its un-shifted version.
2021-03-02 17:50:06 +01:00
|
|
|
|
#endif
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Translate key name to symbol */
|
|
|
|
|
|
xkb_keysym_t sym = xkb_keysym_from_name(key, 0);
|
|
|
|
|
|
if (sym == XKB_KEY_NoSymbol) {
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [%s]: %s: ]%s: key is not a valid XKB key name",
|
|
|
|
|
|
path, lineno, section, option, key);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
goto err;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
tll_push_back(
|
|
|
|
|
|
*key_combos,
|
|
|
|
|
|
((struct key_combo){.text = xstrdup(combo), .modifiers = modifiers, .sym = sym}));
|
2020-03-12 17:16:35 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
free(copy);
|
2020-03-12 17:16:35 +01:00
|
|
|
|
return true;
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
err:
|
|
|
|
|
|
tll_foreach(*key_combos, it)
|
|
|
|
|
|
free(it->item.text);
|
|
|
|
|
|
tll_free(*key_combos);
|
|
|
|
|
|
free(copy);
|
|
|
|
|
|
return false;
|
2020-03-12 17:16:35 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-09 22:40:53 +02:00
|
|
|
|
static bool
|
2021-02-07 14:46:29 +01:00
|
|
|
|
has_key_binding_collisions(struct config *conf,
|
|
|
|
|
|
int action, const char *const action_map[],
|
|
|
|
|
|
config_key_binding_list_t *bindings,
|
2020-12-05 11:21:17 +01:00
|
|
|
|
const key_combo_list_t *key_combos,
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
const char *path, unsigned lineno)
|
2020-08-09 22:40:53 +02:00
|
|
|
|
{
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_foreach(*bindings, it) {
|
2020-12-05 11:21:17 +01:00
|
|
|
|
if (it->item.action == action)
|
|
|
|
|
|
continue;
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
tll_foreach(*key_combos, it2) {
|
|
|
|
|
|
const struct config_key_modifiers *mods1 = &it->item.modifiers;
|
|
|
|
|
|
const struct config_key_modifiers *mods2 = &it2->item.modifiers;
|
|
|
|
|
|
|
2020-11-06 19:26:55 +01:00
|
|
|
|
bool shift = mods1->shift == mods2->shift;
|
|
|
|
|
|
bool alt = mods1->alt == mods2->alt;
|
|
|
|
|
|
bool ctrl = mods1->ctrl == mods2->ctrl;
|
|
|
|
|
|
bool meta = mods1->meta == mods2->meta;
|
|
|
|
|
|
bool sym = it->item.sym == it2->item.sym;
|
|
|
|
|
|
|
|
|
|
|
|
if (shift && alt && ctrl && meta && sym) {
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
bool has_pipe = it->item.pipe.cmd != NULL;
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: %s already mapped to '%s%s%s%s'",
|
|
|
|
|
|
path, lineno, it2->item.text,
|
2021-02-07 14:46:29 +01:00
|
|
|
|
action_map[it->item.action],
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
has_pipe ? " [" : "",
|
|
|
|
|
|
has_pipe ? it->item.pipe.cmd : "",
|
|
|
|
|
|
has_pipe ? "]" : "");
|
|
|
|
|
|
return true;
|
2020-08-09 22:40:53 +02:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
2020-08-09 22:40:53 +02:00
|
|
|
|
|
2020-07-30 18:57:21 +02:00
|
|
|
|
static int
|
|
|
|
|
|
argv_compare(char *const *argv1, char *const *argv2)
|
|
|
|
|
|
{
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(argv1 != NULL);
|
|
|
|
|
|
xassert(argv2 != NULL);
|
2020-07-30 18:57:21 +02:00
|
|
|
|
|
|
|
|
|
|
for (size_t i = 0; ; i++) {
|
|
|
|
|
|
if (argv1[i] == NULL && argv2[i] == NULL)
|
|
|
|
|
|
return 0;
|
|
|
|
|
|
if (argv1[i] == NULL)
|
|
|
|
|
|
return -1;
|
|
|
|
|
|
if (argv2[i] == NULL)
|
|
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
|
|
|
|
int ret = strcmp(argv1[i], argv2[i]);
|
|
|
|
|
|
if (ret != 0)
|
|
|
|
|
|
return ret;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-09 13:52:33 +00:00
|
|
|
|
BUG("unexpected loop break");
|
2020-07-30 18:57:21 +02:00
|
|
|
|
return 1;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-11-06 19:27:46 +01:00
|
|
|
|
/*
|
|
|
|
|
|
* Parses a key binding value on the form
|
|
|
|
|
|
* "[cmd-to-exec arg1 arg2] Mods+Key"
|
|
|
|
|
|
*
|
|
|
|
|
|
* and extracts 'cmd-to-exec' and its arguments.
|
|
|
|
|
|
*
|
|
|
|
|
|
* Input:
|
|
|
|
|
|
* - value: raw string, on the form mention above
|
|
|
|
|
|
* - cmd: pointer to string to will be allocated and filled with
|
|
|
|
|
|
* 'cmd-to-exec arg1 arg2'
|
|
|
|
|
|
* - argv: point to array of string. Array will be allocated. Will be
|
|
|
|
|
|
* filled with {'cmd-to-exec', 'arg1', 'arg2', NULL}
|
|
|
|
|
|
*
|
|
|
|
|
|
* Returns:
|
|
|
|
|
|
* - ssize_t, number of bytes to strip from 'value' to remove the '[]'
|
|
|
|
|
|
* enclosed cmd and its arguments, including any subsequent
|
|
|
|
|
|
* whitespace characters. I.e. if 'value' is "[cmd] BTN_RIGHT", the
|
|
|
|
|
|
* return value is 6 (strlen("[cmd] ")).
|
|
|
|
|
|
* - cmd: allocated string containing "cmd arg1 arg2...". Caller frees.
|
|
|
|
|
|
* - argv: allocatd array containing {"cmd", "arg1", "arg2", NULL}. Caller frees.
|
|
|
|
|
|
*/
|
|
|
|
|
|
static ssize_t
|
|
|
|
|
|
pipe_argv_from_string(const char *value, char **cmd, char ***argv,
|
|
|
|
|
|
struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
*cmd = NULL;
|
|
|
|
|
|
*argv = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
if (value[0] != '[')
|
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
|
|
|
|
const char *pipe_cmd_end = strrchr(value, ']');
|
|
|
|
|
|
if (pipe_cmd_end == NULL) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: unclosed '['", path, lineno);
|
|
|
|
|
|
return -1;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
size_t pipe_len = pipe_cmd_end - value - 1;
|
|
|
|
|
|
*cmd = xstrndup(&value[1], pipe_len);
|
|
|
|
|
|
|
|
|
|
|
|
if (!tokenize_cmdline(*cmd, argv)) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: syntax error in command line", path, lineno);
|
|
|
|
|
|
free(*cmd);
|
|
|
|
|
|
return -1;
|
|
|
|
|
|
}
|
2020-09-10 18:17:47 +02:00
|
|
|
|
|
2020-11-06 19:27:46 +01:00
|
|
|
|
ssize_t remove_len = pipe_cmd_end + 1 - value;
|
|
|
|
|
|
value = pipe_cmd_end + 1;
|
|
|
|
|
|
while (isspace(*value)) {
|
|
|
|
|
|
value++;
|
|
|
|
|
|
remove_len++;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return remove_len;
|
2020-09-10 18:17:47 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
static bool NOINLINE
|
|
|
|
|
|
parse_key_binding_section(
|
|
|
|
|
|
const char *section, const char *key, const char *value,
|
|
|
|
|
|
int action_count, const char *const action_map[static action_count],
|
|
|
|
|
|
config_key_binding_list_t *bindings,
|
|
|
|
|
|
struct config *conf, const char *path, unsigned lineno)
|
2020-03-09 20:03:04 +01:00
|
|
|
|
{
|
2020-11-06 19:27:46 +01:00
|
|
|
|
char *pipe_cmd;
|
|
|
|
|
|
char **pipe_argv;
|
2020-07-15 17:28:09 +02:00
|
|
|
|
|
2020-11-06 19:27:46 +01:00
|
|
|
|
ssize_t pipe_remove_len = pipe_argv_from_string(
|
|
|
|
|
|
value, &pipe_cmd, &pipe_argv, conf, path, lineno);
|
2020-07-30 18:53:51 +02:00
|
|
|
|
|
2020-11-06 19:27:46 +01:00
|
|
|
|
if (pipe_remove_len < 0)
|
|
|
|
|
|
return false;
|
2020-07-15 17:28:09 +02:00
|
|
|
|
|
2020-11-06 19:27:46 +01:00
|
|
|
|
value += pipe_remove_len;
|
2020-07-15 13:32:31 +02:00
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
for (int action = 0; action < action_count; action++) {
|
|
|
|
|
|
if (action_map[action] == NULL)
|
2020-03-12 10:46:27 +01:00
|
|
|
|
continue;
|
|
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
if (strcmp(key, action_map[action]) != 0)
|
2020-03-09 20:03:04 +01:00
|
|
|
|
continue;
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Unset binding */
|
2020-03-18 14:52:04 +01:00
|
|
|
|
if (strcasecmp(value, "none") == 0) {
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_foreach(*bindings, it) {
|
2020-07-15 16:39:07 +02:00
|
|
|
|
if (it->item.action == action) {
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
if (it->item.pipe.master_copy) {
|
|
|
|
|
|
free(it->item.pipe.cmd);
|
|
|
|
|
|
free(it->item.pipe.argv);
|
|
|
|
|
|
}
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_remove(*bindings, it);
|
2020-07-15 16:39:07 +02:00
|
|
|
|
}
|
|
|
|
|
|
}
|
2020-07-30 18:53:51 +02:00
|
|
|
|
free(pipe_argv);
|
|
|
|
|
|
free(pipe_cmd);
|
2020-03-12 17:16:35 +01:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
2020-03-09 20:03:04 +01:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
key_combo_list_t key_combos = tll_init();
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
if (!parse_key_combos(
|
|
|
|
|
|
conf, value, &key_combos, section, key, path, lineno) ||
|
2021-02-07 14:46:29 +01:00
|
|
|
|
has_key_binding_collisions(
|
2021-04-05 14:33:44 +02:00
|
|
|
|
conf, action, action_map, bindings, &key_combos,
|
2021-02-07 14:46:29 +01:00
|
|
|
|
path, lineno))
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
{
|
2020-07-30 18:53:51 +02:00
|
|
|
|
free(pipe_argv);
|
|
|
|
|
|
free(pipe_cmd);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
free_key_combo_list(&key_combos);
|
2020-03-09 20:03:04 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Remove existing bindings for this action+pipe */
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_foreach(*bindings, it) {
|
2020-07-15 16:39:07 +02:00
|
|
|
|
if (it->item.action == action &&
|
2020-07-30 18:53:51 +02:00
|
|
|
|
((it->item.pipe.argv == NULL && pipe_argv == NULL) ||
|
|
|
|
|
|
(it->item.pipe.argv != NULL && pipe_argv != NULL &&
|
|
|
|
|
|
argv_compare(it->item.pipe.argv, pipe_argv) == 0)))
|
2020-07-15 16:39:07 +02:00
|
|
|
|
{
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
if (it->item.pipe.master_copy) {
|
|
|
|
|
|
free(it->item.pipe.cmd);
|
|
|
|
|
|
free(it->item.pipe.argv);
|
|
|
|
|
|
}
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_remove(*bindings, it);
|
2020-07-15 16:39:07 +02:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Emit key bindings */
|
|
|
|
|
|
bool first = true;
|
|
|
|
|
|
tll_foreach(key_combos, it) {
|
2021-02-07 14:46:29 +01:00
|
|
|
|
struct config_key_binding binding = {
|
2020-07-15 16:39:07 +02:00
|
|
|
|
.action = action,
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
.modifiers = it->item.modifiers,
|
|
|
|
|
|
.sym = it->item.sym,
|
2020-07-30 18:53:51 +02:00
|
|
|
|
.pipe = {
|
|
|
|
|
|
.cmd = pipe_cmd,
|
|
|
|
|
|
.argv = pipe_argv,
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
.master_copy = first,
|
2020-07-30 18:53:51 +02:00
|
|
|
|
},
|
2020-07-15 16:39:07 +02:00
|
|
|
|
};
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_push_back(*bindings, binding);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
first = false;
|
2020-07-15 16:39:07 +02:00
|
|
|
|
}
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
free_key_combo_list(&key_combos);
|
2020-03-09 20:03:04 +01:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%u: [%s]: %s: invalid action",
|
|
|
|
|
|
path, lineno, section, key);
|
2020-09-08 19:09:36 +02:00
|
|
|
|
free(pipe_cmd);
|
|
|
|
|
|
free(pipe_argv);
|
2020-03-09 20:03:04 +01:00
|
|
|
|
return false;
|
2021-02-07 14:46:29 +01:00
|
|
|
|
}
|
2020-03-09 20:03:04 +01:00
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_key_bindings(
|
|
|
|
|
|
const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
return parse_key_binding_section(
|
|
|
|
|
|
"key-bindings", key, value, BIND_ACTION_KEY_COUNT, binding_action_map,
|
|
|
|
|
|
&conf->bindings.key, conf, path, lineno);
|
2020-03-09 20:03:04 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-07-29 17:27:01 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_search_bindings(
|
|
|
|
|
|
const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
2021-04-05 14:50:21 +02:00
|
|
|
|
static const char *const search_binding_action_map[] = {
|
|
|
|
|
|
[BIND_ACTION_SEARCH_NONE] = NULL,
|
|
|
|
|
|
[BIND_ACTION_SEARCH_CANCEL] = "cancel",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_COMMIT] = "commit",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_FIND_PREV] = "find-prev",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_FIND_NEXT] = "find-next",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EDIT_LEFT] = "cursor-left",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EDIT_LEFT_WORD] = "cursor-left-word",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EDIT_RIGHT] = "cursor-right",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EDIT_RIGHT_WORD] = "cursor-right-word",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EDIT_HOME] = "cursor-home",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EDIT_END] = "cursor-end",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_DELETE_PREV] = "delete-prev",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_DELETE_PREV_WORD] = "delete-prev-word",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_DELETE_NEXT] = "delete-next",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_DELETE_NEXT_WORD] = "delete-next-word",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EXTEND_WORD] = "extend-to-word-boundary",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_EXTEND_WORD_WS] = "extend-to-next-whitespace",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_CLIPBOARD_PASTE] = "clipboard-paste",
|
|
|
|
|
|
[BIND_ACTION_SEARCH_PRIMARY_PASTE] = "primary-paste",
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
static_assert(ALEN(search_binding_action_map) == BIND_ACTION_SEARCH_COUNT,
|
|
|
|
|
|
"search binding action map size mismatch");
|
|
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
return parse_key_binding_section(
|
|
|
|
|
|
"search-bindings", key, value, BIND_ACTION_SEARCH_COUNT,
|
|
|
|
|
|
search_binding_action_map, &conf->bindings.search, conf, path, lineno);
|
2020-07-29 17:27:01 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-30 12:43:59 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_url_bindings(
|
|
|
|
|
|
const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
2021-04-05 14:50:21 +02:00
|
|
|
|
static const char *const url_binding_action_map[] = {
|
|
|
|
|
|
[BIND_ACTION_URL_NONE] = NULL,
|
|
|
|
|
|
[BIND_ACTION_URL_CANCEL] = "cancel",
|
|
|
|
|
|
[BIND_ACTION_URL_TOGGLE_URL_ON_JUMP_LABEL] = "toggle-url-visible",
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
static_assert(ALEN(url_binding_action_map) == BIND_ACTION_URL_COUNT,
|
|
|
|
|
|
"URL binding action map size mismatch");
|
|
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
return parse_key_binding_section(
|
|
|
|
|
|
"url-bindings", key, value, BIND_ACTION_URL_COUNT,
|
|
|
|
|
|
url_binding_action_map, &conf->bindings.url, conf, path, lineno);
|
2021-01-30 12:43:59 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_mouse_combos(struct config *conf, const char *combos, key_combo_list_t *key_combos,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(tll_length(*key_combos) == 0);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
char *copy = xstrdup(combos);
|
|
|
|
|
|
|
|
|
|
|
|
for (char *tok_ctx = NULL, *combo = strtok_r(copy, " ", &tok_ctx);
|
|
|
|
|
|
combo != NULL;
|
|
|
|
|
|
combo = strtok_r(NULL, " ", &tok_ctx))
|
|
|
|
|
|
{
|
2020-08-23 07:42:20 +02:00
|
|
|
|
struct config_key_modifiers modifiers = {0};
|
2020-08-10 19:39:37 +02:00
|
|
|
|
char *key = strrchr(combo, '+');
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
if (key == NULL) {
|
|
|
|
|
|
/* No modifiers */
|
|
|
|
|
|
key = combo;
|
|
|
|
|
|
} else {
|
2020-08-10 19:39:37 +02:00
|
|
|
|
*key = '\0';
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
if (!parse_modifiers(conf, combo, key - combo, &modifiers, path, lineno))
|
|
|
|
|
|
goto err;
|
2020-08-11 10:44:27 +02:00
|
|
|
|
if (modifiers.shift) {
|
2020-09-09 19:04:24 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: Shift cannot be used in mouse bindings",
|
|
|
|
|
|
path, lineno);
|
2020-08-11 10:44:27 +02:00
|
|
|
|
goto err;
|
|
|
|
|
|
}
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
key++; /* Skip past the '+' */
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-11-06 19:28:38 +01:00
|
|
|
|
size_t count = 1;
|
2020-08-10 19:39:37 +02:00
|
|
|
|
{
|
|
|
|
|
|
char *_count = strrchr(key, '-');
|
|
|
|
|
|
if (_count != NULL) {
|
|
|
|
|
|
*_count = '\0';
|
|
|
|
|
|
_count++;
|
|
|
|
|
|
|
|
|
|
|
|
errno = 0;
|
|
|
|
|
|
char *end;
|
|
|
|
|
|
unsigned long value = strtoul(_count, &end, 10);
|
|
|
|
|
|
if (_count[0] == '\0' || *end != '\0' || errno != 0) {
|
|
|
|
|
|
if (errno != 0)
|
|
|
|
|
|
LOG_AND_NOTIFY_ERRNO(
|
|
|
|
|
|
"%s:%d: %s: invalid click count", path, lineno, _count);
|
|
|
|
|
|
else
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: %s: invalid click count", path, lineno, _count);
|
|
|
|
|
|
goto err;
|
|
|
|
|
|
}
|
|
|
|
|
|
count = value;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
static const struct {
|
|
|
|
|
|
const char *name;
|
|
|
|
|
|
int code;
|
|
|
|
|
|
} map[] = {
|
|
|
|
|
|
{"BTN_LEFT", BTN_LEFT},
|
|
|
|
|
|
{"BTN_RIGHT", BTN_RIGHT},
|
|
|
|
|
|
{"BTN_MIDDLE", BTN_MIDDLE},
|
|
|
|
|
|
{"BTN_SIDE", BTN_SIDE},
|
|
|
|
|
|
{"BTN_EXTRA", BTN_EXTRA},
|
|
|
|
|
|
{"BTN_FORWARD", BTN_FORWARD},
|
|
|
|
|
|
{"BTN_BACK", BTN_BACK},
|
|
|
|
|
|
{"BTN_TASK", BTN_TASK},
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
int button = 0;
|
|
|
|
|
|
for (size_t i = 0; i < ALEN(map); i++) {
|
|
|
|
|
|
if (strcmp(key, map[i].name) == 0) {
|
|
|
|
|
|
button = map[i].code;
|
|
|
|
|
|
break;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
if (button == 0) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: %s: invalid mouse button name", path, lineno, key);
|
|
|
|
|
|
goto err;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
struct key_combo new = {
|
|
|
|
|
|
.text = xstrdup(combo),
|
|
|
|
|
|
.modifiers = modifiers,
|
|
|
|
|
|
.m = {
|
|
|
|
|
|
.button = button,
|
2020-08-10 19:39:37 +02:00
|
|
|
|
.count = count,
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
},
|
|
|
|
|
|
};
|
|
|
|
|
|
tll_push_back(*key_combos, new);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
free(copy);
|
|
|
|
|
|
return true;
|
|
|
|
|
|
|
|
|
|
|
|
err:
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_foreach(*key_combos, it) {
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
free(it->item.text);
|
2021-02-07 14:46:29 +01:00
|
|
|
|
tll_remove(*key_combos, it);
|
|
|
|
|
|
}
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
free(copy);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static bool
|
|
|
|
|
|
has_mouse_binding_collisions(struct config *conf, const key_combo_list_t *key_combos,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
|
|
|
|
|
tll_foreach(conf->bindings.mouse, it) {
|
|
|
|
|
|
tll_foreach(*key_combos, it2) {
|
|
|
|
|
|
const struct config_key_modifiers *mods1 = &it->item.modifiers;
|
|
|
|
|
|
const struct config_key_modifiers *mods2 = &it2->item.modifiers;
|
|
|
|
|
|
|
2020-11-06 19:26:55 +01:00
|
|
|
|
bool shift = mods1->shift == mods2->shift;
|
|
|
|
|
|
bool alt = mods1->alt == mods2->alt;
|
|
|
|
|
|
bool ctrl = mods1->ctrl == mods2->ctrl;
|
|
|
|
|
|
bool meta = mods1->meta == mods2->meta;
|
|
|
|
|
|
bool button = it->item.button == it2->item.m.button;
|
|
|
|
|
|
bool count = it->item.count == it2->item.m.count;
|
|
|
|
|
|
|
|
|
|
|
|
if (shift && alt && ctrl && meta && button && count) {
|
2020-11-06 19:29:23 +01:00
|
|
|
|
bool has_pipe = it->item.pipe.cmd != NULL;
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: %s already mapped to '%s%s%s%s'",
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
path, lineno, it2->item.text,
|
2020-11-06 19:29:23 +01:00
|
|
|
|
binding_action_map[it->item.action],
|
|
|
|
|
|
has_pipe ? " [" : "",
|
|
|
|
|
|
has_pipe ? it->item.pipe.cmd : "",
|
|
|
|
|
|
has_pipe ? "]" : "");
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-03-12 10:20:05 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_mouse_bindings(
|
|
|
|
|
|
const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
2020-11-06 19:29:23 +01:00
|
|
|
|
char *pipe_cmd;
|
|
|
|
|
|
char **pipe_argv;
|
|
|
|
|
|
|
|
|
|
|
|
ssize_t pipe_remove_len = pipe_argv_from_string(
|
|
|
|
|
|
value, &pipe_cmd, &pipe_argv, conf, path, lineno);
|
|
|
|
|
|
|
|
|
|
|
|
if (pipe_remove_len < 0)
|
|
|
|
|
|
return false;
|
|
|
|
|
|
|
|
|
|
|
|
value += pipe_remove_len;
|
|
|
|
|
|
|
2020-08-11 09:55:33 +02:00
|
|
|
|
for (enum bind_action_normal action = 0;
|
|
|
|
|
|
action < BIND_ACTION_COUNT;
|
|
|
|
|
|
action++)
|
|
|
|
|
|
{
|
2020-03-12 10:46:27 +01:00
|
|
|
|
if (binding_action_map[action] == NULL)
|
|
|
|
|
|
continue;
|
|
|
|
|
|
|
2020-03-12 10:20:05 +01:00
|
|
|
|
if (strcmp(key, binding_action_map[action]) != 0)
|
|
|
|
|
|
continue;
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Unset binding */
|
|
|
|
|
|
if (strcasecmp(value, "none") == 0) {
|
2020-07-15 16:39:07 +02:00
|
|
|
|
tll_foreach(conf->bindings.mouse, it) {
|
2020-11-06 19:29:23 +01:00
|
|
|
|
if (it->item.action == action) {
|
|
|
|
|
|
if (it->item.pipe.master_copy) {
|
|
|
|
|
|
free(it->item.pipe.cmd);
|
|
|
|
|
|
free(it->item.pipe.argv);
|
|
|
|
|
|
}
|
2020-07-15 16:39:07 +02:00
|
|
|
|
tll_remove(conf->bindings.mouse, it);
|
2020-11-06 19:29:23 +01:00
|
|
|
|
}
|
2020-07-15 16:39:07 +02:00
|
|
|
|
}
|
2020-11-06 19:29:23 +01:00
|
|
|
|
free(pipe_argv);
|
|
|
|
|
|
free(pipe_cmd);
|
2020-03-12 10:46:27 +01:00
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
key_combo_list_t key_combos = tll_init();
|
|
|
|
|
|
if (!parse_mouse_combos(conf, value, &key_combos, path, lineno) ||
|
|
|
|
|
|
has_mouse_binding_collisions(conf, &key_combos, path, lineno))
|
|
|
|
|
|
{
|
2020-11-06 19:29:23 +01:00
|
|
|
|
free(pipe_argv);
|
|
|
|
|
|
free(pipe_cmd);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
free_key_combo_list(&key_combos);
|
2020-08-09 22:40:53 +02:00
|
|
|
|
return false;
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
}
|
2020-08-09 22:40:53 +02:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Remove existing bindings for this action */
|
2020-08-09 22:40:53 +02:00
|
|
|
|
tll_foreach(conf->bindings.mouse, it) {
|
2020-11-06 19:29:23 +01:00
|
|
|
|
if (it->item.action == action &&
|
|
|
|
|
|
((it->item.pipe.argv == NULL && pipe_argv == NULL) ||
|
|
|
|
|
|
(it->item.pipe.argv != NULL && pipe_argv != NULL &&
|
|
|
|
|
|
argv_compare(it->item.pipe.argv, pipe_argv) == 0)))
|
|
|
|
|
|
{
|
|
|
|
|
|
if (it->item.pipe.master_copy) {
|
|
|
|
|
|
free(it->item.pipe.cmd);
|
|
|
|
|
|
free(it->item.pipe.argv);
|
|
|
|
|
|
}
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
tll_remove(conf->bindings.mouse, it);
|
2020-08-09 22:40:53 +02:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
/* Emit mouse bindings */
|
2020-11-06 19:29:23 +01:00
|
|
|
|
bool first = true;
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
tll_foreach(key_combos, it) {
|
2020-08-09 22:40:53 +02:00
|
|
|
|
struct config_mouse_binding binding = {
|
|
|
|
|
|
.action = action,
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
.modifiers = it->item.modifiers,
|
|
|
|
|
|
.button = it->item.m.button,
|
|
|
|
|
|
.count = it->item.m.count,
|
2020-11-06 19:29:23 +01:00
|
|
|
|
.pipe = {
|
|
|
|
|
|
.cmd = pipe_cmd,
|
|
|
|
|
|
.argv = pipe_argv,
|
|
|
|
|
|
.master_copy = first,
|
|
|
|
|
|
},
|
2020-08-09 22:40:53 +02:00
|
|
|
|
};
|
|
|
|
|
|
tll_push_back(conf->bindings.mouse, binding);
|
2020-11-06 19:29:23 +01:00
|
|
|
|
first = false;
|
2020-08-09 22:40:53 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
free_key_combo_list(&key_combos);
|
2020-08-09 22:40:53 +02:00
|
|
|
|
return true;
|
2020-03-12 10:20:05 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%u: [mouse-bindings]: %s: invalid key", path, lineno, key);
|
2020-11-06 19:29:23 +01:00
|
|
|
|
free(pipe_argv);
|
|
|
|
|
|
free(pipe_cmd);
|
2020-03-12 10:20:05 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-17 16:46:54 +01:00
|
|
|
|
static bool
|
|
|
|
|
|
parse_section_tweak(
|
|
|
|
|
|
const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno)
|
|
|
|
|
|
{
|
2020-09-13 17:59:56 +02:00
|
|
|
|
if (strcmp(key, "scaling-filter") == 0) {
|
|
|
|
|
|
static const struct {
|
|
|
|
|
|
const char *name;
|
|
|
|
|
|
enum fcft_scaling_filter filter;
|
|
|
|
|
|
} filters[] = {
|
|
|
|
|
|
{"none", FCFT_SCALING_FILTER_NONE},
|
|
|
|
|
|
{"nearest", FCFT_SCALING_FILTER_NEAREST},
|
|
|
|
|
|
{"bilinear", FCFT_SCALING_FILTER_BILINEAR},
|
|
|
|
|
|
{"cubic", FCFT_SCALING_FILTER_CUBIC},
|
|
|
|
|
|
{"lanczos3", FCFT_SCALING_FILTER_LANCZOS3},
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
for (size_t i = 0; i < ALEN(filters); i++) {
|
|
|
|
|
|
if (strcmp(value, filters[i].name) == 0) {
|
|
|
|
|
|
conf->tweak.fcft_filter = filters[i].filter;
|
|
|
|
|
|
LOG_WARN("tweak: scaling-filter=%s", filters[i].name);
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [tweak]: %s: invalid 'scaling-filter' value, "
|
|
|
|
|
|
"expected one of 'none', 'nearest', 'bilinear', 'cubic' or "
|
|
|
|
|
|
"'lanczos3'", path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "allow-overflowing-double-width-glyphs") == 0) {
|
2020-09-03 17:37:44 +02:00
|
|
|
|
conf->tweak.allow_overflowing_double_width_glyphs = str_to_bool(value);
|
2020-11-13 17:49:23 +01:00
|
|
|
|
if (!conf->tweak.allow_overflowing_double_width_glyphs)
|
|
|
|
|
|
LOG_WARN("tweak: disabled overflowing double-width glyphs");
|
2020-09-12 19:52:52 +02:00
|
|
|
|
}
|
2020-09-03 17:37:44 +02:00
|
|
|
|
|
2020-09-12 19:52:52 +02:00
|
|
|
|
else if (strcmp(key, "damage-whole-window") == 0) {
|
2020-09-06 17:52:07 +02:00
|
|
|
|
conf->tweak.damage_whole_window = str_to_bool(value);
|
2020-09-12 19:52:52 +02:00
|
|
|
|
if (conf->tweak.damage_whole_window)
|
|
|
|
|
|
LOG_WARN("tweak: damage whole window");
|
|
|
|
|
|
}
|
2020-09-06 17:52:07 +02:00
|
|
|
|
|
2020-09-03 17:37:44 +02:00
|
|
|
|
else if (strcmp(key, "render-timer") == 0) {
|
2020-08-13 18:35:17 +02:00
|
|
|
|
if (strcmp(value, "none") == 0) {
|
|
|
|
|
|
conf->tweak.render_timer_osd = false;
|
|
|
|
|
|
conf->tweak.render_timer_log = false;
|
|
|
|
|
|
} else if (strcmp(value, "osd") == 0) {
|
|
|
|
|
|
conf->tweak.render_timer_osd = true;
|
|
|
|
|
|
conf->tweak.render_timer_log = false;
|
|
|
|
|
|
} else if (strcmp(value, "log") == 0) {
|
|
|
|
|
|
conf->tweak.render_timer_osd = false;
|
|
|
|
|
|
conf->tweak.render_timer_log = true;
|
|
|
|
|
|
} else if (strcmp(value, "both") == 0) {
|
|
|
|
|
|
conf->tweak.render_timer_osd = true;
|
|
|
|
|
|
conf->tweak.render_timer_log = true;
|
|
|
|
|
|
} else {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [tweak]: %s: invalid 'render-timer' value, "
|
|
|
|
|
|
"expected one of 'none', 'osd', 'log' or 'both'",
|
|
|
|
|
|
path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "delayed-render-lower") == 0) {
|
2020-03-17 16:46:54 +01:00
|
|
|
|
unsigned long ns;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &ns)) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: expected an integer, got '%s'", path, lineno, value);
|
2020-03-17 16:46:54 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
if (ns > 16666666) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: timeout must not exceed 16ms", path, lineno);
|
2020-03-17 16:46:54 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->tweak.delayed_render_lower_ns = ns;
|
|
|
|
|
|
LOG_WARN("tweak: delayed-render-lower=%lu", ns);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
else if (strcmp(key, "delayed-render-upper") == 0) {
|
|
|
|
|
|
unsigned long ns;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &ns)) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: expected an integer, got '%s'", path, lineno, value);
|
2020-03-17 16:46:54 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
if (ns > 16666666) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: timeout must not exceed 16ms", path, lineno);
|
2020-03-17 16:46:54 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->tweak.delayed_render_upper_ns = ns;
|
|
|
|
|
|
LOG_WARN("tweak: delayed-render-upper=%lu", ns);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-25 20:48:02 +01:00
|
|
|
|
else if (strcmp(key, "max-shm-pool-size-mb") == 0) {
|
|
|
|
|
|
unsigned long mb;
|
|
|
|
|
|
if (!str_to_ulong(value, 10, &mb)) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: expected an integer, got '%s'", path, lineno, value);
|
2020-03-25 20:48:02 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->tweak.max_shm_pool_size = min(mb * 1024 * 1024, INT32_MAX);
|
2020-08-06 23:20:46 +02:00
|
|
|
|
LOG_WARN("tweak: max-shm-pool-size=%lld bytes",
|
|
|
|
|
|
(long long)conf->tweak.max_shm_pool_size);
|
2020-03-25 20:48:02 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-08 10:27:35 +01:00
|
|
|
|
else if (strcmp(key, "box-drawing-base-thickness") == 0) {
|
|
|
|
|
|
double base_thickness;
|
|
|
|
|
|
if (!str_to_double(value, &base_thickness)) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR(
|
|
|
|
|
|
"%s:%d: [tweak]: box-drawing-base-thickness: "
|
|
|
|
|
|
"expected a decimal value, got '%s'", path, lineno, value);
|
|
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
conf->tweak.box_drawing_base_thickness = base_thickness;
|
|
|
|
|
|
LOG_WARN("tweak: box-drawing-base-thickness=%f",
|
|
|
|
|
|
conf->tweak.box_drawing_base_thickness);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-17 16:46:54 +01:00
|
|
|
|
else {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%u: [tweak]: %s: invalid key", path, lineno, key);
|
2020-03-17 16:46:54 +01:00
|
|
|
|
return false;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
return true;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
static bool
|
2020-07-31 17:07:14 +02:00
|
|
|
|
parse_config_file(FILE *f, struct config *conf, const char *path, bool errors_are_fatal)
|
2019-07-16 11:52:22 +02:00
|
|
|
|
{
|
|
|
|
|
|
enum section {
|
|
|
|
|
|
SECTION_MAIN,
|
2020-07-29 17:41:24 +02:00
|
|
|
|
SECTION_SCROLLBACK,
|
2019-07-21 11:31:16 +02:00
|
|
|
|
SECTION_COLORS,
|
2019-07-22 20:15:14 +02:00
|
|
|
|
SECTION_CURSOR,
|
2020-08-04 07:33:15 +02:00
|
|
|
|
SECTION_MOUSE,
|
2020-03-02 18:42:49 +01:00
|
|
|
|
SECTION_CSD,
|
2020-03-09 20:03:04 +01:00
|
|
|
|
SECTION_KEY_BINDINGS,
|
2020-07-29 17:27:01 +02:00
|
|
|
|
SECTION_SEARCH_BINDINGS,
|
2021-01-30 12:43:59 +01:00
|
|
|
|
SECTION_URL_BINDINGS,
|
2020-03-12 10:20:05 +01:00
|
|
|
|
SECTION_MOUSE_BINDINGS,
|
2020-03-17 16:46:54 +01:00
|
|
|
|
SECTION_TWEAK,
|
2020-03-09 20:03:04 +01:00
|
|
|
|
SECTION_COUNT,
|
2019-07-16 11:52:22 +02:00
|
|
|
|
} section = SECTION_MAIN;
|
|
|
|
|
|
|
|
|
|
|
|
/* Function pointer, called for each key/value line */
|
|
|
|
|
|
typedef bool (*parser_fun_t)(
|
2019-07-17 10:12:14 +02:00
|
|
|
|
const char *key, const char *value, struct config *conf,
|
|
|
|
|
|
const char *path, unsigned lineno);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
2020-03-09 20:03:04 +01:00
|
|
|
|
static const struct {
|
|
|
|
|
|
parser_fun_t fun;
|
|
|
|
|
|
const char *name;
|
|
|
|
|
|
} section_info[] = {
|
2020-07-29 17:27:01 +02:00
|
|
|
|
[SECTION_MAIN] = {&parse_section_main, "main"},
|
2020-07-29 17:41:24 +02:00
|
|
|
|
[SECTION_SCROLLBACK] = {&parse_section_scrollback, "scrollback"},
|
2020-07-29 17:27:01 +02:00
|
|
|
|
[SECTION_COLORS] = {&parse_section_colors, "colors"},
|
|
|
|
|
|
[SECTION_CURSOR] = {&parse_section_cursor, "cursor"},
|
2020-08-04 07:33:15 +02:00
|
|
|
|
[SECTION_MOUSE] = {&parse_section_mouse, "mouse"},
|
2020-07-29 17:27:01 +02:00
|
|
|
|
[SECTION_CSD] = {&parse_section_csd, "csd"},
|
|
|
|
|
|
[SECTION_KEY_BINDINGS] = {&parse_section_key_bindings, "key-bindings"},
|
|
|
|
|
|
[SECTION_SEARCH_BINDINGS] = {&parse_section_search_bindings, "search-bindings"},
|
2021-01-30 12:43:59 +01:00
|
|
|
|
[SECTION_URL_BINDINGS] = {&parse_section_url_bindings, "url-bindings"},
|
2020-07-29 17:27:01 +02:00
|
|
|
|
[SECTION_MOUSE_BINDINGS] = {&parse_section_mouse_bindings, "mouse-bindings"},
|
|
|
|
|
|
[SECTION_TWEAK] = {&parse_section_tweak, "tweak"},
|
2019-07-16 11:52:22 +02:00
|
|
|
|
};
|
|
|
|
|
|
|
2020-03-09 20:03:04 +01:00
|
|
|
|
static_assert(ALEN(section_info) == SECTION_COUNT, "section info array size mismatch");
|
2019-07-17 10:12:14 +02:00
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
unsigned lineno = 0;
|
2020-03-02 18:48:29 +01:00
|
|
|
|
|
2019-07-21 11:46:46 +02:00
|
|
|
|
char *_line = NULL;
|
2020-03-02 18:48:29 +01:00
|
|
|
|
size_t count = 0;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
2020-07-31 17:07:14 +02:00
|
|
|
|
#define error_or_continue() \
|
|
|
|
|
|
{ \
|
|
|
|
|
|
if (errors_are_fatal) \
|
|
|
|
|
|
goto err; \
|
|
|
|
|
|
else \
|
|
|
|
|
|
continue; \
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
while (true) {
|
|
|
|
|
|
errno = 0;
|
|
|
|
|
|
lineno++;
|
|
|
|
|
|
|
2019-07-21 11:46:46 +02:00
|
|
|
|
ssize_t ret = getline(&_line, &count, f);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
|
|
|
|
|
if (ret < 0) {
|
|
|
|
|
|
if (errno != 0) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERRNO("failed to read from configuration");
|
|
|
|
|
|
if (errors_are_fatal)
|
|
|
|
|
|
goto err;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
break;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-07-28 19:55:09 +02:00
|
|
|
|
/* Strip leading whitespace */
|
2019-07-21 11:46:46 +02:00
|
|
|
|
char *line = _line;
|
|
|
|
|
|
{
|
|
|
|
|
|
while (isspace(*line))
|
|
|
|
|
|
line++;
|
|
|
|
|
|
if (line[0] != '\0') {
|
|
|
|
|
|
char *end = line + strlen(line) - 1;
|
|
|
|
|
|
while (isspace(*end))
|
|
|
|
|
|
end--;
|
|
|
|
|
|
*(end + 1) = '\0';
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* Empty line, or comment */
|
2020-03-02 18:48:29 +01:00
|
|
|
|
if (line[0] == '\0' || line[0] == '#')
|
2019-07-21 11:46:46 +02:00
|
|
|
|
continue;
|
|
|
|
|
|
|
2021-01-03 14:08:25 -05:00
|
|
|
|
/* Split up into key/value pair + trailing comment separated by blank */
|
|
|
|
|
|
char *key_value = line;
|
|
|
|
|
|
char *comment = line;
|
|
|
|
|
|
while (comment[0] != '\0') {
|
|
|
|
|
|
const char c = comment[0];
|
|
|
|
|
|
comment++;
|
|
|
|
|
|
if (isblank(c) && comment[0] == '#') {
|
|
|
|
|
|
comment[0] = '\0'; /* Terminate key/value pair */
|
|
|
|
|
|
comment++;
|
|
|
|
|
|
break;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
2020-07-28 19:55:09 +02:00
|
|
|
|
|
2019-07-21 11:46:46 +02:00
|
|
|
|
/* Check for new section */
|
2020-07-28 19:55:09 +02:00
|
|
|
|
if (key_value[0] == '[') {
|
|
|
|
|
|
char *end = strchr(key_value, ']');
|
2019-07-21 11:31:16 +02:00
|
|
|
|
if (end == NULL) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: syntax error: %s", path, lineno, key_value);
|
|
|
|
|
|
error_or_continue();
|
2019-07-21 11:31:16 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
*end = '\0';
|
|
|
|
|
|
|
2020-03-09 20:03:04 +01:00
|
|
|
|
section = SECTION_COUNT;
|
|
|
|
|
|
for (enum section i = 0; i < SECTION_COUNT; i++) {
|
2020-07-28 19:55:09 +02:00
|
|
|
|
if (strcmp(&key_value[1], section_info[i].name) == 0) {
|
2020-03-09 20:03:04 +01:00
|
|
|
|
section = i;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
if (section == SECTION_COUNT) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: invalid section name: %s", path, lineno, &key_value[1]);
|
|
|
|
|
|
error_or_continue();
|
2019-07-21 11:31:16 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-09 20:03:04 +01:00
|
|
|
|
/* Process next line */
|
2019-07-21 11:31:16 +02:00
|
|
|
|
continue;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-10-07 18:34:48 +02:00
|
|
|
|
if (section >= SECTION_COUNT) {
|
|
|
|
|
|
/* Last section name was invalid; ignore all keys in it */
|
|
|
|
|
|
continue;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-07-28 19:55:09 +02:00
|
|
|
|
char *key = strtok(key_value, "=");
|
|
|
|
|
|
if (key == NULL) {
|
2020-07-31 17:07:14 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERR("%s:%d: syntax error: no key specified", path, lineno);
|
|
|
|
|
|
error_or_continue();
|
2020-07-28 19:55:09 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-17 10:12:14 +02:00
|
|
|
|
char *value = strtok(NULL, "\n");
|
2020-07-28 19:55:09 +02:00
|
|
|
|
if (value == NULL) {
|
|
|
|
|
|
/* Empty value, i.e. "key=" */
|
|
|
|
|
|
value = key + strlen(key);
|
|
|
|
|
|
}
|
2019-07-17 10:12:14 +02:00
|
|
|
|
|
2019-07-21 11:46:46 +02:00
|
|
|
|
/* Strip trailing whitespace from key (leading stripped earlier) */
|
2020-08-02 20:01:07 +02:00
|
|
|
|
{
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(!isspace(*key));
|
2019-07-21 11:46:46 +02:00
|
|
|
|
|
2019-07-17 10:12:14 +02:00
|
|
|
|
char *end = key + strlen(key) - 1;
|
|
|
|
|
|
while (isspace(*end))
|
|
|
|
|
|
end--;
|
|
|
|
|
|
*(end + 1) = '\0';
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-07-28 19:55:09 +02:00
|
|
|
|
/* Strip leading+trailing whitespace from value */
|
2019-07-17 10:12:14 +02:00
|
|
|
|
{
|
|
|
|
|
|
while (isspace(*value))
|
|
|
|
|
|
value++;
|
|
|
|
|
|
|
2020-07-28 19:55:09 +02:00
|
|
|
|
if (value[0] != '\0') {
|
|
|
|
|
|
char *end = value + strlen(value) - 1;
|
|
|
|
|
|
while (isspace(*end))
|
|
|
|
|
|
end--;
|
|
|
|
|
|
*(end + 1) = '\0';
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
2019-07-17 10:12:14 +02:00
|
|
|
|
|
2020-07-28 19:55:09 +02:00
|
|
|
|
LOG_DBG("section=%s, key='%s', value='%s', comment='%s'",
|
|
|
|
|
|
section_info[section].name, key, value, comment);
|
2019-07-17 10:12:14 +02:00
|
|
|
|
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(section >= 0 && section < SECTION_COUNT);
|
2020-10-07 18:34:48 +02:00
|
|
|
|
|
2020-03-09 20:03:04 +01:00
|
|
|
|
parser_fun_t section_parser = section_info[section].fun;
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(section_parser != NULL);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
|
2019-07-21 11:46:46 +02:00
|
|
|
|
if (!section_parser(key, value, conf, path, lineno))
|
2020-07-31 17:07:14 +02:00
|
|
|
|
error_or_continue();
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2020-03-02 18:48:29 +01:00
|
|
|
|
free(_line);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
return true;
|
2019-07-21 11:46:46 +02:00
|
|
|
|
|
|
|
|
|
|
err:
|
|
|
|
|
|
free(_line);
|
|
|
|
|
|
return false;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2019-12-14 12:59:06 +01:00
|
|
|
|
static char *
|
|
|
|
|
|
get_server_socket_path(void)
|
|
|
|
|
|
{
|
|
|
|
|
|
const char *xdg_runtime = getenv("XDG_RUNTIME_DIR");
|
|
|
|
|
|
if (xdg_runtime == NULL)
|
2020-08-04 23:28:16 +01:00
|
|
|
|
return xstrdup("/tmp/foot.sock");
|
2019-12-14 12:59:06 +01:00
|
|
|
|
|
2020-08-02 13:10:31 +02:00
|
|
|
|
const char *wayland_display = getenv("WAYLAND_DISPLAY");
|
|
|
|
|
|
if (wayland_display == NULL) {
|
2020-08-04 23:28:16 +01:00
|
|
|
|
return xasprintf("%s/foot.sock", xdg_runtime);
|
2020-08-02 13:10:31 +02:00
|
|
|
|
}
|
2020-03-09 18:47:10 +01:00
|
|
|
|
|
2020-08-04 23:28:16 +01:00
|
|
|
|
return xasprintf("%s/foot-%s.sock", xdg_runtime, wayland_display);
|
2019-12-14 12:59:06 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
static void
|
|
|
|
|
|
add_default_key_bindings(struct config *conf)
|
|
|
|
|
|
{
|
|
|
|
|
|
#define add_binding(action, mods, sym) \
|
|
|
|
|
|
do { \
|
|
|
|
|
|
tll_push_back( \
|
|
|
|
|
|
conf->bindings.key, \
|
2021-02-07 14:46:29 +01:00
|
|
|
|
((struct config_key_binding){action, mods, sym})); \
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
} while (0)
|
|
|
|
|
|
|
|
|
|
|
|
const struct config_key_modifiers shift = {.shift = true};
|
|
|
|
|
|
const struct config_key_modifiers ctrl = {.ctrl = true};
|
|
|
|
|
|
const struct config_key_modifiers ctrl_shift = {.ctrl = true, .shift = true};
|
|
|
|
|
|
|
2020-12-08 19:58:02 +01:00
|
|
|
|
add_binding(BIND_ACTION_SCROLLBACK_UP_PAGE, shift, XKB_KEY_Page_Up);
|
|
|
|
|
|
add_binding(BIND_ACTION_SCROLLBACK_DOWN_PAGE, shift, XKB_KEY_Page_Down);
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
add_binding(BIND_ACTION_CLIPBOARD_COPY, ctrl_shift, XKB_KEY_c);
|
|
|
|
|
|
add_binding(BIND_ACTION_CLIPBOARD_PASTE, ctrl_shift, XKB_KEY_v);
|
2020-10-10 10:27:42 +02:00
|
|
|
|
add_binding(BIND_ACTION_PRIMARY_PASTE, shift, XKB_KEY_Insert);
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
add_binding(BIND_ACTION_SEARCH_START, ctrl_shift, XKB_KEY_r);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
add_binding(BIND_ACTION_FONT_SIZE_UP, ctrl, XKB_KEY_plus);
|
|
|
|
|
|
add_binding(BIND_ACTION_FONT_SIZE_UP, ctrl, XKB_KEY_equal);
|
|
|
|
|
|
add_binding(BIND_ACTION_FONT_SIZE_UP, ctrl, XKB_KEY_KP_Add);
|
|
|
|
|
|
add_binding(BIND_ACTION_FONT_SIZE_DOWN, ctrl, XKB_KEY_minus);
|
|
|
|
|
|
add_binding(BIND_ACTION_FONT_SIZE_DOWN, ctrl, XKB_KEY_KP_Subtract);
|
|
|
|
|
|
add_binding(BIND_ACTION_FONT_SIZE_RESET, ctrl, XKB_KEY_0);
|
|
|
|
|
|
add_binding(BIND_ACTION_FONT_SIZE_RESET, ctrl, XKB_KEY_KP_0);
|
input: rewrite of how we match foot’s own key bindings
Bindings are matched in one out of three ways:
* By translated (by XKB) symbols
* By untranslated symbols
* By raw key codes
A translated symbol is affected by pressed modifiers, some of which
can be “consumed”. Consumed modifiers to not partake in the comparison
with the binding’s modifiers. In this mode, ctrl+shift+2 maps to
ctrl+@ on a US layout.
Untranslated symbols, or un-shifted symbols refer to the “base” symbol
of the pressed key, i.e. it’s unaffected by modifiers. In this mode,
consumed modifiers *do* partake in the comparison with the binding’s
modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout.
More examples: ctrl+shift+u maps to ctrl+U in the translated lookup,
while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup.
Finally, we also match raw key codes. This allows our bindings to work
using the same physical keys when the user switches between latin and
non-latin layouts.
This means key bindings in foot.ini *must* not include both +shift+
and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it
cannot be triggered. Unfortunately, this was how you were supposed to
write bindings up until now... so, we try to detect such bindings, log
a deprecation warning and then “fix” the binding for the user.
When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are
valid, and will work. The latter is preferred though, since we cannot
detect the raw key code for the former variant. Personally, I also
prefer the latter one because it is more explicit; it’s more obvious
which keys are involved.
However, in some cases it makes more sense to use the other
variant. Typically for non-letter combos.
2021-02-27 20:42:31 +01:00
|
|
|
|
add_binding(BIND_ACTION_SPAWN_TERMINAL, ctrl_shift, XKB_KEY_n);
|
|
|
|
|
|
add_binding(BIND_ACTION_SHOW_URLS_LAUNCH, ctrl_shift, XKB_KEY_u);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
#undef add_binding
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
|
add_default_search_bindings(struct config *conf)
|
|
|
|
|
|
{
|
|
|
|
|
|
#define add_binding(action, mods, sym) \
|
|
|
|
|
|
do { \
|
|
|
|
|
|
tll_push_back( \
|
|
|
|
|
|
conf->bindings.search, \
|
2021-02-07 14:46:29 +01:00
|
|
|
|
((struct config_key_binding){action, mods, sym})); \
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
} while (0)
|
|
|
|
|
|
|
2020-08-23 07:42:20 +02:00
|
|
|
|
const struct config_key_modifiers none = {0};
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
const struct config_key_modifiers alt = {.alt = true};
|
|
|
|
|
|
const struct config_key_modifiers ctrl = {.ctrl = true};
|
2020-11-01 12:39:57 +01:00
|
|
|
|
const struct config_key_modifiers shift = {.shift = true};
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
const struct config_key_modifiers ctrl_shift = {.ctrl = true, .shift = true};
|
|
|
|
|
|
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_CANCEL, ctrl, XKB_KEY_g);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_CANCEL, none, XKB_KEY_Escape);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_COMMIT, none, XKB_KEY_Return);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_FIND_PREV, ctrl, XKB_KEY_r);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_FIND_NEXT, ctrl, XKB_KEY_s);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_LEFT, none, XKB_KEY_Left);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_LEFT, ctrl, XKB_KEY_b);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_LEFT_WORD, ctrl, XKB_KEY_Left);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_LEFT_WORD, alt, XKB_KEY_b);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_RIGHT, none, XKB_KEY_Right);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_RIGHT, ctrl, XKB_KEY_f);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_RIGHT_WORD, ctrl, XKB_KEY_Right);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_RIGHT_WORD, alt, XKB_KEY_f);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_HOME, none, XKB_KEY_Home);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_HOME, ctrl, XKB_KEY_a);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_END, none, XKB_KEY_End);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EDIT_END, ctrl, XKB_KEY_e);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_DELETE_PREV, none, XKB_KEY_BackSpace);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_DELETE_PREV_WORD, ctrl, XKB_KEY_BackSpace);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_DELETE_PREV_WORD, alt, XKB_KEY_BackSpace);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_DELETE_NEXT, none, XKB_KEY_Delete);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_DELETE_NEXT_WORD, ctrl, XKB_KEY_Delete);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_DELETE_NEXT_WORD, alt, XKB_KEY_d);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EXTEND_WORD, ctrl, XKB_KEY_w);
|
2021-02-27 21:33:52 +01:00
|
|
|
|
add_binding(BIND_ACTION_SEARCH_EXTEND_WORD_WS, ctrl_shift, XKB_KEY_w);
|
2020-11-01 12:39:57 +01:00
|
|
|
|
add_binding(BIND_ACTION_SEARCH_CLIPBOARD_PASTE, ctrl, XKB_KEY_v);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_CLIPBOARD_PASTE, ctrl, XKB_KEY_y);
|
|
|
|
|
|
add_binding(BIND_ACTION_SEARCH_PRIMARY_PASTE, shift, XKB_KEY_Insert);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
#undef add_binding
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-30 12:43:59 +01:00
|
|
|
|
static void
|
|
|
|
|
|
add_default_url_bindings(struct config *conf)
|
|
|
|
|
|
{
|
|
|
|
|
|
#define add_binding(action, mods, sym) \
|
|
|
|
|
|
do { \
|
|
|
|
|
|
tll_push_back( \
|
|
|
|
|
|
conf->bindings.url, \
|
2021-02-07 14:46:29 +01:00
|
|
|
|
((struct config_key_binding){action, mods, sym})); \
|
2021-01-30 12:43:59 +01:00
|
|
|
|
} while (0)
|
|
|
|
|
|
|
|
|
|
|
|
const struct config_key_modifiers none = {0};
|
|
|
|
|
|
const struct config_key_modifiers ctrl = {.ctrl = true};
|
|
|
|
|
|
|
|
|
|
|
|
add_binding(BIND_ACTION_URL_CANCEL, ctrl, XKB_KEY_g);
|
2021-02-04 19:40:24 +01:00
|
|
|
|
add_binding(BIND_ACTION_URL_CANCEL, ctrl, XKB_KEY_d);
|
2021-01-30 12:43:59 +01:00
|
|
|
|
add_binding(BIND_ACTION_URL_CANCEL, none, XKB_KEY_Escape);
|
2021-02-14 16:58:34 +01:00
|
|
|
|
add_binding(BIND_ACTION_URL_TOGGLE_URL_ON_JUMP_LABEL, none, XKB_KEY_t);
|
2021-01-30 12:43:59 +01:00
|
|
|
|
|
|
|
|
|
|
#undef add_binding
|
|
|
|
|
|
}
|
|
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
static void
|
|
|
|
|
|
add_default_mouse_bindings(struct config *conf)
|
|
|
|
|
|
{
|
|
|
|
|
|
#define add_binding(action, mods, btn, count) \
|
|
|
|
|
|
do { \
|
|
|
|
|
|
tll_push_back( \
|
|
|
|
|
|
conf->bindings.mouse, \
|
2020-11-06 19:29:23 +01:00
|
|
|
|
((struct config_mouse_binding){action, mods, btn, count, {0}})); \
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
} while (0)
|
|
|
|
|
|
|
2020-08-23 07:42:20 +02:00
|
|
|
|
const struct config_key_modifiers none = {0};
|
2020-08-11 09:55:33 +02:00
|
|
|
|
const struct config_key_modifiers ctrl = {.ctrl = true};
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
add_binding(BIND_ACTION_PRIMARY_PASTE, none, BTN_MIDDLE, 1);
|
2020-08-11 09:55:33 +02:00
|
|
|
|
add_binding(BIND_ACTION_SELECT_BEGIN, none, BTN_LEFT, 1);
|
2020-08-11 10:17:19 +02:00
|
|
|
|
add_binding(BIND_ACTION_SELECT_BEGIN_BLOCK, ctrl, BTN_LEFT, 1);
|
|
|
|
|
|
add_binding(BIND_ACTION_SELECT_EXTEND, none, BTN_RIGHT, 1);
|
2021-01-06 11:11:46 +01:00
|
|
|
|
add_binding(BIND_ACTION_SELECT_EXTEND_CHAR_WISE, ctrl, BTN_RIGHT, 1);
|
2020-08-11 09:55:33 +02:00
|
|
|
|
add_binding(BIND_ACTION_SELECT_WORD, none, BTN_LEFT, 2);
|
|
|
|
|
|
add_binding(BIND_ACTION_SELECT_WORD_WS, ctrl, BTN_LEFT, 2);
|
2020-08-11 10:17:19 +02:00
|
|
|
|
add_binding(BIND_ACTION_SELECT_ROW, none, BTN_LEFT, 3);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
|
|
|
|
|
|
#undef add_binding
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-17 10:12:14 +02:00
|
|
|
|
bool
|
2020-09-08 19:17:29 +02:00
|
|
|
|
config_load(struct config *conf, const char *conf_path,
|
|
|
|
|
|
user_notifications_t *initial_user_notifications, bool errors_are_fatal)
|
2019-07-16 11:52:22 +02:00
|
|
|
|
{
|
2019-07-17 10:12:14 +02:00
|
|
|
|
bool ret = false;
|
|
|
|
|
|
|
|
|
|
|
|
*conf = (struct config) {
|
2021-02-26 16:23:43 -05:00
|
|
|
|
.term = xstrdup(DEFAULT_TERM),
|
2019-07-17 09:29:56 +02:00
|
|
|
|
.shell = get_shell(),
|
2020-08-04 23:28:16 +01:00
|
|
|
|
.title = xstrdup("foot"),
|
|
|
|
|
|
.app_id = xstrdup("foot"),
|
2020-10-09 19:44:23 +02:00
|
|
|
|
.word_delimiters = xwcsdup(L",│`|:\"'()[]{}<>"),
|
2021-02-13 11:42:40 +01:00
|
|
|
|
.jump_label_letters = xwcsdup(L"sadfjklewcmpgh"),
|
2020-09-08 19:17:29 +02:00
|
|
|
|
.size = {
|
|
|
|
|
|
.type = CONF_SIZE_PX,
|
2020-11-30 02:24:38 +00:00
|
|
|
|
.width = 700,
|
|
|
|
|
|
.height = 500,
|
2020-09-08 19:17:29 +02:00
|
|
|
|
},
|
2020-02-15 19:00:56 +01:00
|
|
|
|
.pad_x = 2,
|
|
|
|
|
|
.pad_y = 2,
|
2021-01-21 15:14:43 +01:00
|
|
|
|
.resize_delay_ms = 100,
|
2021-04-17 21:57:08 +02:00
|
|
|
|
.bold_in_bright = {
|
|
|
|
|
|
.enabled = false,
|
|
|
|
|
|
.palette_based = false,
|
|
|
|
|
|
},
|
2020-12-10 18:22:48 +01:00
|
|
|
|
.bell_action = BELL_ACTION_NONE,
|
2020-03-26 19:39:12 +01:00
|
|
|
|
.startup_mode = STARTUP_WINDOWED,
|
2020-10-20 21:04:47 +02:00
|
|
|
|
.fonts = {tll_init(), tll_init(), tll_init(), tll_init()},
|
2021-01-07 17:00:58 +01:00
|
|
|
|
.line_height = { .pt = 0, .px = -1, },
|
|
|
|
|
|
.letter_spacing = { .pt = 0, .px = 0, },
|
|
|
|
|
|
.horizontal_letter_offset = {.pt = 0, .px = 0, },
|
|
|
|
|
|
.vertical_letter_offset = {.pt = 0, .px = 0, },
|
2021-04-09 23:19:20 +02:00
|
|
|
|
.box_drawings_uses_font_glyphs = false,
|
2020-12-17 12:05:22 +01:00
|
|
|
|
.dpi_aware = DPI_AWARE_AUTO, /* DPI-aware when scaling-factor == 1 */
|
2020-07-25 14:31:45 +02:00
|
|
|
|
.scrollback = {
|
|
|
|
|
|
.lines = 1000,
|
|
|
|
|
|
.indicator = {
|
2020-07-27 20:02:51 +02:00
|
|
|
|
.position = SCROLLBACK_INDICATOR_POSITION_RELATIVE,
|
2020-07-28 19:56:53 +02:00
|
|
|
|
.format = SCROLLBACK_INDICATOR_FORMAT_TEXT,
|
|
|
|
|
|
.text = wcsdup(L""),
|
2020-07-25 14:31:45 +02:00
|
|
|
|
},
|
2020-09-29 09:50:17 +02:00
|
|
|
|
.multiplier = 3.,
|
2020-07-25 14:31:45 +02:00
|
|
|
|
},
|
2019-07-21 11:06:28 +02:00
|
|
|
|
.colors = {
|
|
|
|
|
|
.fg = default_foreground,
|
|
|
|
|
|
.bg = default_background,
|
2021-04-07 08:07:43 +02:00
|
|
|
|
.table = {
|
2019-07-21 11:06:28 +02:00
|
|
|
|
default_regular[0],
|
|
|
|
|
|
default_regular[1],
|
|
|
|
|
|
default_regular[2],
|
|
|
|
|
|
default_regular[3],
|
|
|
|
|
|
default_regular[4],
|
|
|
|
|
|
default_regular[5],
|
|
|
|
|
|
default_regular[6],
|
|
|
|
|
|
default_regular[7],
|
2021-04-07 08:07:43 +02:00
|
|
|
|
|
2019-07-21 11:06:28 +02:00
|
|
|
|
default_bright[0],
|
|
|
|
|
|
default_bright[1],
|
|
|
|
|
|
default_bright[2],
|
|
|
|
|
|
default_bright[3],
|
|
|
|
|
|
default_bright[4],
|
|
|
|
|
|
default_bright[5],
|
|
|
|
|
|
default_bright[6],
|
|
|
|
|
|
default_bright[7],
|
|
|
|
|
|
},
|
2019-08-16 22:06:06 +02:00
|
|
|
|
.alpha = 0xffff,
|
2020-08-12 18:53:32 +02:00
|
|
|
|
.selection_fg = 0x80000000, /* Use default bg */
|
|
|
|
|
|
.selection_bg = 0x80000000, /* Use default fg */
|
2021-02-06 10:35:48 +01:00
|
|
|
|
.use_custom = {
|
|
|
|
|
|
.selection = false,
|
2021-02-06 11:10:40 +01:00
|
|
|
|
.jump_label = false,
|
|
|
|
|
|
.url = false,
|
2021-02-06 10:35:48 +01:00
|
|
|
|
},
|
2019-07-21 11:06:28 +02:00
|
|
|
|
},
|
2019-07-22 20:15:14 +02:00
|
|
|
|
|
|
|
|
|
|
.cursor = {
|
|
|
|
|
|
.style = CURSOR_BLOCK,
|
2020-06-30 17:45:34 +02:00
|
|
|
|
.blink = false,
|
2019-07-23 18:54:58 +02:00
|
|
|
|
.color = {
|
|
|
|
|
|
.text = 0,
|
|
|
|
|
|
.cursor = 0,
|
|
|
|
|
|
},
|
2021-04-30 20:31:47 +02:00
|
|
|
|
.beam_thickness = {.pt = 1.5},
|
2019-07-22 20:15:14 +02:00
|
|
|
|
},
|
2020-08-04 07:33:15 +02:00
|
|
|
|
.mouse = {
|
|
|
|
|
|
.hide_when_typing = false,
|
2020-09-15 19:09:00 +02:00
|
|
|
|
.alternate_scroll_mode = true,
|
2020-08-04 07:33:15 +02:00
|
|
|
|
},
|
2020-03-02 18:42:49 +01:00
|
|
|
|
.csd = {
|
|
|
|
|
|
.preferred = CONF_CSD_PREFER_SERVER,
|
|
|
|
|
|
.title_height = 26,
|
|
|
|
|
|
.border_width = 5,
|
2020-03-06 19:11:31 +01:00
|
|
|
|
.button_width = 26,
|
2020-03-02 18:42:49 +01:00
|
|
|
|
},
|
|
|
|
|
|
|
2019-07-29 20:13:26 +02:00
|
|
|
|
.render_worker_count = sysconf(_SC_NPROCESSORS_ONLN),
|
2019-12-14 12:59:06 +01:00
|
|
|
|
.server_socket_path = get_server_socket_path(),
|
2020-02-03 19:58:32 +01:00
|
|
|
|
.presentation_timings = false,
|
2021-01-16 11:26:03 +01:00
|
|
|
|
.selection_target = SELECTION_TARGET_PRIMARY,
|
2020-02-03 19:58:32 +01:00
|
|
|
|
.hold_at_exit = false,
|
2020-12-08 19:19:55 +01:00
|
|
|
|
.notify = {
|
|
|
|
|
|
.raw_cmd = NULL,
|
|
|
|
|
|
.argv = NULL,
|
|
|
|
|
|
},
|
2020-03-17 16:46:54 +01:00
|
|
|
|
|
2021-02-16 11:24:57 +01:00
|
|
|
|
.osc8_underline = OSC8_UNDERLINE_URL_MODE,
|
2021-02-14 21:29:22 +01:00
|
|
|
|
|
2020-03-17 16:46:54 +01:00
|
|
|
|
.tweak = {
|
2020-09-13 17:59:56 +02:00
|
|
|
|
.fcft_filter = FCFT_SCALING_FILTER_LANCZOS3,
|
2020-11-13 17:49:23 +01:00
|
|
|
|
.allow_overflowing_double_width_glyphs = true,
|
2020-03-17 16:46:54 +01:00
|
|
|
|
.delayed_render_lower_ns = 500000, /* 0.5ms */
|
|
|
|
|
|
.delayed_render_upper_ns = 16666666 / 2, /* half a frame period (60Hz) */
|
2020-03-25 20:48:02 +01:00
|
|
|
|
.max_shm_pool_size = 512 * 1024 * 1024,
|
2020-08-13 18:35:17 +02:00
|
|
|
|
.render_timer_osd = false,
|
|
|
|
|
|
.render_timer_log = false,
|
2020-09-06 17:52:07 +02:00
|
|
|
|
.damage_whole_window = false,
|
2021-01-11 13:06:48 +01:00
|
|
|
|
.box_drawing_base_thickness = 0.04,
|
2020-03-17 16:46:54 +01:00
|
|
|
|
},
|
2020-07-29 19:42:12 +02:00
|
|
|
|
|
2020-07-30 18:57:21 +02:00
|
|
|
|
.notifications = tll_init(),
|
2019-07-16 11:52:22 +02:00
|
|
|
|
};
|
|
|
|
|
|
|
2021-04-07 08:07:43 +02:00
|
|
|
|
/* Initialize the color cube */
|
|
|
|
|
|
{
|
|
|
|
|
|
/* First 16 entries correspond to the "regular" and "bright"
|
|
|
|
|
|
* colors, and have already been initialized */
|
|
|
|
|
|
|
|
|
|
|
|
/* Then follows 216 RGB shades */
|
|
|
|
|
|
for (size_t r = 0; r < 6; r++) {
|
|
|
|
|
|
for (size_t g = 0; g < 6; g++) {
|
|
|
|
|
|
for (size_t b = 0; b < 6; b++) {
|
|
|
|
|
|
conf->colors.table[16 + r * 6 * 6 + g * 6 + b]
|
|
|
|
|
|
= r * 51 << 16 | g * 51 << 8 | b * 51;
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* And finally 24 shades of gray */
|
|
|
|
|
|
for (size_t i = 0; i < 24; i++)
|
|
|
|
|
|
conf->colors.table[232 + i] = i * 11 << 16 | i * 11 << 8 | i * 11;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-12-08 19:19:55 +01:00
|
|
|
|
conf->notify.raw_cmd = xstrdup(
|
|
|
|
|
|
"notify-send -a foot -i foot ${title} ${body}");
|
|
|
|
|
|
tokenize_cmdline(conf->notify.raw_cmd, &conf->notify.argv);
|
|
|
|
|
|
|
2021-01-31 14:27:13 +01:00
|
|
|
|
conf->url_launch.raw_cmd = xstrdup("xdg-open ${url}");
|
|
|
|
|
|
tokenize_cmdline(conf->url_launch.raw_cmd, &conf->url_launch.argv);
|
|
|
|
|
|
|
2021-02-07 14:52:04 +01:00
|
|
|
|
tll_foreach(*initial_user_notifications, it) {
|
2020-09-08 19:17:29 +02:00
|
|
|
|
tll_push_back(conf->notifications, it->item);
|
2021-02-07 14:52:04 +01:00
|
|
|
|
tll_remove(*initial_user_notifications, it);
|
|
|
|
|
|
}
|
2020-09-08 19:17:29 +02:00
|
|
|
|
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
add_default_key_bindings(conf);
|
|
|
|
|
|
add_default_search_bindings(conf);
|
2021-01-30 12:43:59 +01:00
|
|
|
|
add_default_url_bindings(conf);
|
config: key/mouse bindings: refactor: less parsing in keyboard_enter()
This simplifies the handling of mouse and keyboard bindings.
Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.
The following has changed:
* The bindings in the config struct is now *one* key combo per
entry. Previously, it was one *action* per entry, and each entry
had one or more key combos.
Doing it this way makes it easier when converting the binding in the
keyboard enter event (which previously had to expand the combos
anyway).
* The bindings in the config struct no longer contains any unparsed
strings.
A key binding contains a decoded 'modifier' struct (which specifies
whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
binding to be used).
It also contains a decoded XKB keysym.
* A mouse binding in the config struct is similar to a key binding,
except it contains the button, and click count instead of the XKB
key sym.
* The modifiers in the user-specified key combo is decoded at config
time, by using the pre-defined XKB constants
XKB_MOD_NAME_<modifier>.
The result is stored in a 'modifiers' struct, which is just a
collection of booleans; one for each supported modifier.
The supported modifiers are: shift, ctrl, alt and meta/super.
* The key sym is decoded at config time using
xkb_keysym_from_name(). This call does *not* depend on a keymap.
* The mouse button is decoded at config time using a hardcoded mapping
table (just like before).
* The click count is currently hard-coded to 1.
* In the keyboard enter event, all we need to do is pre-compute the
xkb_mod_mask_t variable for each key/mouse binding, and find all the
*key codes* that map to the (already decoded) symbol.
For mouse bindings, the modifiers are the *only* reason we convert
the mouse bindings at all.
In fact, on button events, we check if the seat has a keyboard. If
not, we use the mouse bindings from the configuration directly, and
simply filter out those with a non-empty set of modifiers.
2020-08-10 19:00:03 +02:00
|
|
|
|
add_default_mouse_bindings(conf);
|
2020-07-15 16:39:07 +02:00
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
struct config_file conf_file = {.path = NULL, .fd = -1};
|
|
|
|
|
|
if (conf_path != NULL) {
|
|
|
|
|
|
int fd = open(conf_path, O_RDONLY);
|
|
|
|
|
|
if (fd < 0) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERRNO("%s: failed to open", conf_path);
|
2020-07-31 17:07:14 +02:00
|
|
|
|
ret = !errors_are_fatal;
|
2019-12-17 19:08:43 +01:00
|
|
|
|
goto out;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
conf_file.path = xstrdup(conf_path);
|
|
|
|
|
|
conf_file.fd = fd;
|
|
|
|
|
|
} else {
|
2021-03-16 09:54:32 +01:00
|
|
|
|
conf_file = open_config();
|
2020-08-27 19:48:13 +02:00
|
|
|
|
if (conf_file.fd < 0) {
|
|
|
|
|
|
LOG_AND_NOTIFY_ERR("no configuration found, using defaults");
|
|
|
|
|
|
ret = !errors_are_fatal;
|
|
|
|
|
|
goto out;
|
|
|
|
|
|
}
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-16 20:16:00 +00:00
|
|
|
|
xassert(conf_file.path != NULL);
|
|
|
|
|
|
xassert(conf_file.fd >= 0);
|
2020-08-27 19:48:13 +02:00
|
|
|
|
LOG_INFO("loading configuration from %s", conf_file.path);
|
2019-08-12 19:31:21 +02:00
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
FILE *f = fdopen(conf_file.fd, "r");
|
2019-07-16 11:52:22 +02:00
|
|
|
|
if (f == NULL) {
|
2020-08-27 19:48:13 +02:00
|
|
|
|
LOG_AND_NOTIFY_ERRNO("%s: failed to open", conf_file.path);
|
2020-07-31 17:07:14 +02:00
|
|
|
|
ret = !errors_are_fatal;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
goto out;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2020-09-06 14:48:15 +02:00
|
|
|
|
ret = parse_config_file(f, conf, conf_file.path, errors_are_fatal);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
fclose(f);
|
|
|
|
|
|
|
2021-02-06 10:35:48 +01:00
|
|
|
|
conf->colors.use_custom.selection =
|
2020-08-12 18:53:32 +02:00
|
|
|
|
conf->colors.selection_fg >> 24 == 0 &&
|
|
|
|
|
|
conf->colors.selection_bg >> 24 == 0;
|
|
|
|
|
|
|
2020-02-28 18:33:30 +01:00
|
|
|
|
out:
|
2020-12-15 18:55:27 +01:00
|
|
|
|
if (ret && tll_length(conf->fonts[0]) == 0) {
|
|
|
|
|
|
struct config_font font;
|
|
|
|
|
|
if (!config_font_parse("monospace", &font)) {
|
|
|
|
|
|
LOG_ERR("failed to load font 'monospace' - no fonts installed?");
|
|
|
|
|
|
ret = false;
|
|
|
|
|
|
} else
|
|
|
|
|
|
tll_push_back(conf->fonts[0], font);
|
|
|
|
|
|
}
|
2019-12-17 19:08:43 +01:00
|
|
|
|
|
2020-08-27 19:48:13 +02:00
|
|
|
|
free(conf_file.path);
|
2020-08-27 21:11:03 +02:00
|
|
|
|
if (conf_file.fd >= 0)
|
2020-08-27 19:48:13 +02:00
|
|
|
|
close(conf_file.fd);
|
|
|
|
|
|
|
2019-07-17 10:12:14 +02:00
|
|
|
|
return ret;
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
2021-01-31 14:27:13 +01:00
|
|
|
|
static void
|
|
|
|
|
|
free_spawn_template(struct config_spawn_template *template)
|
|
|
|
|
|
{
|
|
|
|
|
|
free(template->raw_cmd);
|
|
|
|
|
|
free(template->argv);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
static void
|
|
|
|
|
|
binding_pipe_free(struct config_binding_pipe *pipe)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (pipe->master_copy) {
|
|
|
|
|
|
free(pipe->cmd);
|
|
|
|
|
|
free(pipe->argv);
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
|
key_binding_free(struct config_key_binding *binding)
|
|
|
|
|
|
{
|
|
|
|
|
|
binding_pipe_free(&binding->pipe);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
|
|
key_binding_list_free(config_key_binding_list_t *bindings)
|
|
|
|
|
|
{
|
|
|
|
|
|
tll_foreach(*bindings, it) {
|
|
|
|
|
|
key_binding_free(&it->item);
|
|
|
|
|
|
tll_remove(*bindings, it);
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-07-16 11:52:22 +02:00
|
|
|
|
void
|
|
|
|
|
|
config_free(struct config conf)
|
|
|
|
|
|
{
|
2019-07-21 11:46:46 +02:00
|
|
|
|
free(conf.term);
|
2019-07-17 09:29:56 +02:00
|
|
|
|
free(conf.shell);
|
2020-04-01 19:59:47 +02:00
|
|
|
|
free(conf.title);
|
2020-04-01 18:40:51 +02:00
|
|
|
|
free(conf.app_id);
|
2020-10-09 19:44:23 +02:00
|
|
|
|
free(conf.word_delimiters);
|
2021-02-13 11:42:40 +01:00
|
|
|
|
free(conf.jump_label_letters);
|
2020-07-28 19:56:53 +02:00
|
|
|
|
free(conf.scrollback.indicator.text);
|
2021-01-31 14:27:13 +01:00
|
|
|
|
free_spawn_template(&conf.notify);
|
|
|
|
|
|
free_spawn_template(&conf.url_launch);
|
2020-10-20 21:04:47 +02:00
|
|
|
|
for (size_t i = 0; i < ALEN(conf.fonts); i++) {
|
2021-02-07 14:52:04 +01:00
|
|
|
|
tll_foreach(conf.fonts[i], it) {
|
2020-10-20 21:04:47 +02:00
|
|
|
|
config_font_destroy(&it->item);
|
2021-02-07 14:52:04 +01:00
|
|
|
|
tll_remove(conf.fonts[i], it);
|
|
|
|
|
|
}
|
2020-10-20 21:04:47 +02:00
|
|
|
|
}
|
2019-12-14 12:59:06 +01:00
|
|
|
|
free(conf.server_socket_path);
|
2020-03-08 12:08:46 +01:00
|
|
|
|
|
2021-02-07 14:46:29 +01:00
|
|
|
|
key_binding_list_free(&conf.bindings.key);
|
|
|
|
|
|
key_binding_list_free(&conf.bindings.search);
|
|
|
|
|
|
key_binding_list_free(&conf.bindings.url);
|
|
|
|
|
|
|
2020-11-06 19:29:23 +01:00
|
|
|
|
tll_foreach(conf.bindings.mouse, it) {
|
2021-02-07 14:46:29 +01:00
|
|
|
|
binding_pipe_free(&it->item.pipe);
|
|
|
|
|
|
tll_remove(conf.bindings.mouse, it);
|
2020-07-15 13:32:31 +02:00
|
|
|
|
}
|
2020-07-15 16:39:07 +02:00
|
|
|
|
|
2020-09-08 19:17:29 +02:00
|
|
|
|
user_notifications_free(&conf.notifications);
|
2019-07-16 11:52:22 +02:00
|
|
|
|
}
|
2020-07-07 10:44:55 +02:00
|
|
|
|
|
2020-12-15 18:55:27 +01:00
|
|
|
|
bool
|
|
|
|
|
|
config_font_parse(const char *pattern, struct config_font *font)
|
2020-07-07 10:44:55 +02:00
|
|
|
|
{
|
|
|
|
|
|
FcPattern *pat = FcNameParse((const FcChar8 *)pattern);
|
2020-12-15 18:55:27 +01:00
|
|
|
|
if (pat == NULL)
|
|
|
|
|
|
return false;
|
2020-07-07 10:44:55 +02:00
|
|
|
|
|
|
|
|
|
|
double pt_size = -1.0;
|
|
|
|
|
|
FcPatternGetDouble(pat, FC_SIZE, 0, &pt_size);
|
|
|
|
|
|
FcPatternRemove(pat, FC_SIZE, 0);
|
|
|
|
|
|
|
|
|
|
|
|
int px_size = -1;
|
|
|
|
|
|
FcPatternGetInteger(pat, FC_PIXEL_SIZE, 0, &px_size);
|
|
|
|
|
|
FcPatternRemove(pat, FC_PIXEL_SIZE, 0);
|
|
|
|
|
|
|
|
|
|
|
|
if (pt_size == -1. && px_size == -1)
|
|
|
|
|
|
pt_size = 8.0;
|
|
|
|
|
|
|
|
|
|
|
|
char *stripped_pattern = (char *)FcNameUnparse(pat);
|
|
|
|
|
|
FcPatternDestroy(pat);
|
|
|
|
|
|
|
2020-12-15 18:55:27 +01:00
|
|
|
|
*font = (struct config_font){
|
2020-07-07 10:44:55 +02:00
|
|
|
|
.pattern = stripped_pattern,
|
|
|
|
|
|
.pt_size = pt_size,
|
2020-12-15 18:55:27 +01:00
|
|
|
|
.px_size = px_size
|
|
|
|
|
|
};
|
|
|
|
|
|
return true;
|
2020-07-07 10:44:55 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
|
config_font_destroy(struct config_font *font)
|
|
|
|
|
|
{
|
|
|
|
|
|
if (font == NULL)
|
|
|
|
|
|
return;
|
|
|
|
|
|
free(font->pattern);
|
|
|
|
|
|
}
|