Stefan Partheymüller

Just as a side note: I hosted a repository at https://github.com/stefanpartheym/mbp15-wifi-driver which contains the wifi driver files from a MacBookPro15,2 (Mojave), maybe that helps.

@MoonPadUSer I'm on a MacBookPro15,2 `ip link show`: ``` 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: docker0: mtu...

@jbf1983 I think you need to rename the .trx .clmb and .txt files. I made a repository containing a script which does that for you: https://github.com/stefanpartheym/mbp15-wifi-driver This will work as...

Ok, so I'm using the following workaround now to suppress these annoying notifications I get in neovim when the LSP throws an exception: ```lua { "folke/noice.nvim", event = "VeryLazy", opts...

Thank you @AlexandrosAlexiou ! I tried it out by cloning the fork locally and setting it up in `nvim-lspconfig`. Works great! The annoying internal errors are gone now. For anyone...

Hi @vricop, the reason why neo-tree does not expand to full screen size after deleting a buffer in LazyVim is not the neo-tree configuration, but rather the way LazyVim deletes...

> I have the same problem. I also find that doing a simple `:bd` command with the neo-tree plugin open and other files open closes nvim completely if I have...

> [...] > With two files open like that, I would think deleting the buffer that's open in the right pane would leave neo-tree open on the left and the...

> Perhaps it may be a good idea to make a pr describing this to the readme documentation or add the utility function to the plugin itself allowing the option...

> > Hi [@vricop](https://github.com/vricop), > > the reason why neo-tree does not expand to full screen size after deleting a buffer in LazyVim is not the neo-tree configuration, but rather...