Justin M. Keyes
Justin M. Keyes
This sounds awesome. Please include a brief explanation of the reflow patch in the commit message (and PR). Why isn't it upstreamed? Are we going to have a merge issue...
For reference, `jumpoptions` was a similar case where we anticipated future options, and we now have 2 flags there. So introducing `foldoptions` makes sense for these kinds of on/off flags....
> Breaks all previous use of vim.opt* metamethods on those options. This (0.8) would be a good time to eliminate `vim.opt` then. We only need `vim.o`. Can merge this meanwhile.
This would not be a new cli parameter `--height`, rather it would look like : :set lines=1 cmdheight=0 , which currently doesn't work right. Also don't think this is TUI-specific.
> What's the thought on how to fix this? Special-case these options or . . . ? That seems reasonable. `vim.o` (and `vim.opt`, but see https://github.com/neovim/neovim/issues/18246 ) should handle options...
This could ~~not~~ be another `action` for `nvim_input_mouse` . Then I guess we will need at least another pseudokey, e.g. ``.
"not" should not have been in my comment, mistaken edit :)
@yatli please report `:version`
via https://github.com/neoclide/coc.nvim/issues/668#issuecomment-481975596 : > turn off 'modeline' in help will avoid this problem. ... [this commit](https://github.com/neovim/neovim/commit/5eaa45547975c652e594d0d6dbe34c1316873dc7) may be the problem. I hoped that 8c7e41f5 would fix this, but NVIM v0.4.0-1197...