| Age | Commit message (Collapse) | Author |
|---|
|
Closes #3818 (parent issue)
Fixes #1808
Fixes #2333
Fixes #2617
Fixes #3548
|
|
|
|
Arch Linux is discussing increasing to 3, so we should probably keep up:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/17
|
|
Do not canonicalize "nonprimary" output for i3bar
|
|
Fixes #5346
|
|
They are newly failing since the previous commit (upgrading to Ubuntu focal),
so instead of debugging what the issue is, let’s just remove them entirely.
Not many i386 users are left, as the world is on amd64 and arm64 these days.
|
|
This is required to satisfy our meson.build minimal Meson version.
|
|
|
|
|
|
We use run_command for conditionals, meaning meson execution should not stop
when the command returns false. This change keeps our meson setup working
throughout the upcoming change of default behavior (check: true).
|
|
Using “meson” instead of “meson setup” results in a warning.
|
|
|
|
This requires --buildtype=debugoptimized (or --buildtype=release, but
optimizations need to be enabled), and will allow us to keep the i3 build free
of warnings during development.
Distributions like Debian build with -D_FORTIFY_SOURCE=2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fixes #5293
|
|
Add "mode" field in binding event
|
|
This does *not* go in the binding object to reflect the same hierarchy
of the config file: a mode is a collection of bindings.
Fixes #5323
|
|
Unlike in the man page, only one --entry-type is reasonable possible.
On using multiple --entry-types and a command offers multiple, duplicates are removed i3-dmenu-desktop.
See more at #5291
added --show-duplicates flag for this
|
|
No changes to the code are needed.
|
|
Fixes #4878
|
|
|
|
Fixes #5282
|
|
there (#5281)
Fixes #5280
|
|
Fixes https://github.com/i3/i3/issues/5257
|
|
Fixes https://github.com/i3/i3/issues/5258
|
|
Fixes https://github.com/i3/i3/issues/5256
|
|
Fixes https://github.com/i3/i3/issues/5272
|
|
Fixes https://github.com/i3/i3/issues/5261
|
|
Previously, the code was directly accessing con->border_style, which circumvents
the special-casing for stacked/tabbed containers that forces window titles even
for title-less containers.
Fixes https://github.com/i3/i3/issues/5269
|
|
|
|
This commit moves subtracting the global gaps from the workspace gaps:
previously, this calculation was done while parsing the configuration
(order dependent), now it’s done at workspace assignment evaluation time.
related to https://github.com/i3/i3/issues/3724
fixes https://github.com/i3/i3/issues/5253
|
|
related to https://github.com/i3/i3/pull/5245
fixes https://github.com/i3/i3/issues/5254
|
|
Currently, containers only consider their neighbors and screen edges.
If >2 containers are in a line, the outer containers adjust from outer gaps, but
the middle containers know nothing of this and only consider the inner gaps.
When the outer gaps differ substantially from the inner gaps, the left-most and
right-most containers are smaller as only they adjust for the larger outer gaps.
This commit changes the rendering: containers are now always inset by their
inner gap settings, and workspace containers is now inset by the outer gap
settings.
The result is that many tiled containers have the same size, and the gaps
overall work as the user might expect them to previous combinations of
outer/inner gap settings still produce the same result, albeit with fixed
outer-most sizes.
fixes https://github.com/Airblader/i3/issues/22
related to https://github.com/i3/i3/issues/3724
Co-authored-by: Cameron Leger <contact@cameronleger.com>
|
|
This reverts commit 6b658f88be50d5251f85eaf6f838d6c67ebaac95.
The commit was misguided: the pixel values are already run through logical_px()
when parsing the configuration directive or command, so they should not be run
through another logical_px() pass at rendering time.
|
|
I noticed the test was flaky before, possibly this fixes it.
related to #3009
|
|
See https://linux.die.net/man/3/vendorshell
The important part is:
> MWM_DECOR_ALL
> All decorations *except* those specified by other flag bits that are set
|
|
This is the last remaining diff from the i3-gaps tree.
related to https://github.com/i3/i3/issues/3724
Tested using the following config with picom:
bar {
i3bar_command i3bar -t
status_command i3status
colors {
# fully transparent text on opaque background:
statusline #ffffff00
background #000000ff
}
}
|
|
|
|
related to https://github.com/i3/i3/issues/3724
|
|
related to https://github.com/i3/i3/issues/3724
fixes https://github.com/i3/i3/issues/1966
|
|
This makes it possible to set a breakpoint in gdb on a line in the function and
get a backtrace of un-initialized surface access.
|
|
|
|
|
|
|
|
I’m still not 100% happy with how the function turned out (it still does too
many things at once), but this seems like an improvement — at least reading and
navigating the code with LSP now works better.
|
