musjj

Would pen pressure support be possible on Windows? I tested this with WSL1 + VcXsrv and the program actually runs pretty well. But as expected, the pen pressure doesn't work...

@daniel-p-gonzalez This works, but neovim fails to launch for some reason (it just launches an empty screen and pressing `ctrl+c` returns me to bash). vim works just fine, though. Maybe...

Looks like this is the fourth(?) PR for this kind of feature now: - https://github.com/ahmedkhalf/project.nvim/pull/56 - https://github.com/ahmedkhalf/project.nvim/pull/62 - https://github.com/ahmedkhalf/project.nvim/pull/88 I guess it's up to @ahmedkhalf to decide on which one...

I'm using a custom autocmd because `open_on_setup` wasn't flexible enough for my needs. But I'm not talking about that, but [this](https://github.com/kyazdani42/nvim-tree.lua/blob/3e49d9b7484e21f0b24ebdf21b8b7af227ea97a6/lua/nvim-tree.lua#L265) code segment: ```lua -- Session that left a NvimTree...

Thanks for the PR, but I'm not sure how it would fix the issue. Does it fix the issue for `open_on_setup` users? I will try to test that too, but...

> we can open a directory and not focus the tree, as per file behaviour > nvim-tree focuses tree on startup when opening a directory Alright I'll test that, but...

Right, I don't think it has anything to do with my issue at all (my issue is with opening a *file*, and so is that other guy's), but I'll test...

It would be nice if we can also specify the repository source, in case we want to build from different branches or entirely different forks.

There seem to be some issues with cursor tracking in the command bar in general, when multigrid is on. For example using [which-key](https://github.com/folke/which-key.nvim)'s `` register preview to paste a text...

This seems to be a working general solution for this problem: http://www.leonerd.org.uk/hacks/fixterms/ There's also the keyboard protocol from Kitty (which apparently fixes some issues with the classic CSI encoding solution):...