distek

I actually think you read the documentation correctly. I'm looking through the nvim source though and it looks like it fires the event before it actually closes the window?: https://github.com/neovim/neovim/blob/b2bb3973d9c7f25acfead2718d74fcf5b1e4551e/src/nvim/window.c#L2776...

Let me test it more at work today and I'll give you a yay or nay on that.

Broke almost immediately. Played with it throughout the day when I could, came up with this: ```lua vim.api.nvim_create_autocmd("WinEnter", { pattern = { "*" }, callback = function() local winCount =...

> You could keep track of and then check if the number of nvim-ide windows is equal to the total number of windows That's what I was doing in the...

@mrjones2014 Not sure if this is your issue but I had to recompile with Packer to get everything working correctly. Also after changing `auto_close` to false (to test that it...

Have to ask, just to be sure, but did you make sure you're back on main?

> Can anyone confirm Same deal in i3. edit: For what it's worth, this is a work around I just came up with for i3: ``` for_window [title="^avizo$"] border none,...

Just a note, and possibly the solution to some of your issues: Despite `swaymsg -t get_inputs` printing the identifier with escaped characters like so: ``` "identifier": "2:10:TPPS\/2_Elan_TrackPoint", ``` Make sure...

As a workaround, though I think this would be nice to have builtin, you could call `require('ide').setup({...})` in a ftplugin and modify the config as needed for the file type....

> what really changes in the workspace, since most components are pretty general to "code editing" I could see this being beneficial if the user's written their own custom component...