bfredl

Mot sure we want window layout to change on expression evaluation, but we could provide a **static** value to disable winbar locally like `%{%}` or whatever would make sense with...

Option to disable an option sounds like an anti-pattern. Id rather just identify a good sentinel value.

Except that 'winbar' already controls whether it is displayed or not, so i think we should rather make that control complete rather than adding a new option only for one...

Well we could use such a thing only for nightly builds, and not for PR runs (whose queue probably is going to be impossible anyway, unless we spinn up a...

Demonstration (pick your two favorite color schemes): ```lua local a = vim.api _G.a = vim.api vim.cmd [[ color wip ]] atema = a.nvim_create_namespace("hösttema") adata = a.nvim__get_hl_defs(0) for k,v in pairs(adata)...

It could be worth looking at the vim patches for adding support in vim 8 terminal. > This could not be another action for nvim_input_mouse Why not? Even if the...

@dsych well there are two pieces here 1) defining the API, probably an event inside nvim_input_mouse, and an ui_option to turn on/off. 2) provide the terminal implementation of this api...

@dsych we can use either a `TimeWatcher` for c code, or the luv timer api if we implement hover logic in lua. What we need to do before that is...

Maybe `strpart()` (with len=1 and chars=trua) can be used?

I think we need to consider screen.c as it has diverged quite significantly. I'd like to separate out `grid.c` from `screen.c` with most of the lowlevel `grid_` functions. Perhaps drawscreen.c...