Tobias S

I come across this bug quite often. Is it still getting worked on? https://www.youtube.com/watch?v=iPfiy0D-LP4

 i've tested: - xrender backend - glx backend - with and without `--experimental-backends` - shadow off and on all behave the same in this regard.

When can we expect a new release? I'm kinda needing this bug to be fixed ASAP.

@Ahacad vue is generally slower than other filetypes in my experience. My solution for this is not using CursorMoved and WinScrolled autocmds and defining the other [default](https://github.com/wellle/context.vim/blob/108644e146c864995288dee7dacf219267917ac1/plugin/context.vim#L47) ones manually. Just...

i was able to not trigger this bug every day by adding this in my alacritty config: ``` key_bindings: - { key: C, mods: Control, mode: Alt, action: None }...

utilizing [mini.ai](https://github.com/echasnovski/mini.ai) i can define it like this: ```lua local ns_utils = require("nvim-surround.utils") local function ns_alias_mini_ai(alias) return function (mode) local s = ns_utils.get_nearest_selections(alias, "change") if not s then return end...

for those like me who want back their old i3 fullscreen behavior for wayland windows can use my [patch](https://gist.github.com/Hippo0o/55ae87e4e8e84a0e1071a75df0e241db) i created from the v1.7 branch for now

@dromse Thanks for the PR. I won't merge it because i don't use i3 or this project for over a year and a half now. I should probably archive this...

this is broken beyond repair. 1. `[con_id=x]` does not work on workspace container 2. `move container to mark x` does not work when marked is parent of current

let's pray https://github.com/swaywm/sway/issues/6903