| Age | Commit message (Collapse) | Author |
|---|
|
musl libc compatibility
|
|
I've tried to make as few changes, as possible.
Usually the reason for using qsort_r is, that you can pass an extra userdata pointer to the
compare function. However, in sway list_sort wrapped qsort_r and always called a wrapper
function for comparing, the wrapper function then had the real compare function as argument.
The only thing, that the wrapper function does, is dereferencing the 'left' and 'right' function
arguments before passing them to the real compare function.
I have renamed list_sort to list_qsort to avoid confusion (so nobody tries to use list_qsort like
list_sort) and removed the wrapper functionality. Now the dereferencing must be done in the
compare function, that gets passed.
Some compare functions were used in both list_sort and list_seq_find. To make the difference
clear, I've added a '_qsort' suffix to the compare functions, that are intended to be used with
the new list_qsort. (In other words: list_qsort is not compatible anymore with list_seq_find).
- Changed and renamed function (it isn't used anywhere but in commands.c, and only for sorting):
compare_set -> compare_set_qsort
- New wrapper functions:
sway_binding_cmp_qsort (for sway_binding_cmp)
sway_mouse_binding_cmp_qsort (for sway_mouse_binding_cmp)
|
|
|
|
config: load_swaybars: Fix name comparison.
|
|
|
|
bar_config.outputs is NULL if no output is explicitly defined in config
(ie. use for for all outputs).
|
|
|
|
Add bar option: swaybar_command <command>
|
|
|
|
|
|
This works by tracking the pids of the child processes in the related
output container and terminating the processes and spawning new ones on
a config reload.
Should solve: #347
|
|
|
|
|
|
|
|
Implement bar option: separator_symbol
|
|
No need to reimplement free_flat_list functionality.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Free bar->bindings
|
|
|
|
Get rid of `config->bar` and define the default bar config options when
a bar is initialized.
|
|
Defined a sway_mouse_binding for clicks on the swaybar
|
|
This makes it possible to define what mouse button key (left|right) to
use for dragging/resizing.
|
|
|
|
This reverts commit 22916e9ebc130dbd365e6403730b9e0857977b8e.
|
|
|
|
|
|
[RFC] Make mouse key used for drag/resize configurable
|
|
|
|
This makes it possible to define what mouse button key (left|right) to
use for dragging/resizing.
|
|
- Flag was ignored. Now it's taken into account.
- Missing trailing slashes in path now behaves properly.
|
|
CMake takes a `FALLBACK_CONFIG_DIR` flag which is the directory where the
standard configuration file `config` is copied at installation.
If loading from typical configuration directories fails, sway loads
FALLBACK_CONFIG_DIR/config (/etc/sway/config by default).
|
|
This will allow the bar {} block to have a different command set (and
also bar { colors { } }.
|
|
|
|
|
|
This is necessary because i3 config files use CSS notation for colors
(i.e. #rrggbb).
|
|
|
|
|
|
Which will match any output.
|
|
This also makes it so that your i3 config is used before
/etc/sway/config.
|
|
This makes escaping the arguments obsolete.
Also avoid dynamic memory allocation for the output id. It only supported ids up
to 99. Now we support up to 999, and take 4 bytes off the stack instead.
|
|
criteria: Add. Learn for_window command.
|
|
|
|
A criteria is a string in the form of `[class="regex.*" title="str"]`.
It is stored in a struct with a list of *tokens* which is a
attribute/value pair (stored as a `crit_token` struct). Most tokens will
also have a precompiled regex stored that will be used during criteria
matching.
for_window command: When a new view is created its metadata is tested
against all stored criteria, and if a match is found the associated
command list is executed.
Unfortunately some metadata is not available in sway at the moment
(specifically `instance`, `window_role` and `urgent`). Any criteria
string that tries to match an unsupported attribute will fail.
(Note that while the criteria code can be used to parse any criteria
string it is currently only used by the `for_window` command.)
|
|
Compare modifiers as well as keys when number of modifiers+keys are the
same (so that e.g. mod1+x != mod4+x).
|
