insidewhy

BTW tested this with `neovim-fuzzy` as the only plugin enabled, and it still happened.

Here is my workaround: ```vim fun s:FuzzyOpener(val) let prev_tabpage = tabpagenr() exe "tabe" a:val let next_tabpage = tabpagenr() exe "tabnext" prev_tabpage lcd - let dir = getcwd() exe "tabnext" next_tabpage...

The correct fix would be to change this bit of code: https://github.com/cloudhead/neovim-fuzzy/blob/53383395befafce802c902c21b54847074454491/plugin/neovim-fuzzy.vim#L221 It would have to store the current tab before running the open command, and then check if the...

Or alternatively it could just not `lcd` at all and instead resolve the path to open with respect to `self.root`.

Yeah this is also bothering me.

@masaeedu Yeah I noticed that, it has a few more implications than being slightly annoying to me and it's initially what lead me here. I've started to do some work...

@Zalastax I've been doing some work on this in VsCodeVim... it maintains it's own undo stack separate from vscode. If you push ctrl-Z you get code's undo and "u" is...

@Zalastax You could stop vscode creating an undo stack by passing `{ undoStopAfter: false, undoStopAfter: false }` to every single edit API call. IMO creating a new undo stack separate...

Yeah same here, basically makes this project unusable. Weirdly my files are all in `client` (including `package.json`) and it even complains about a file in the directory above `client`. My...

I don't see the error until I type `gd` somewhere to go to a definition. At which stage I see the EACCESS error in my console and it fails to...