Thore Strassburg

Sounds good. This feature will then lead to the issue to make a decision how the notifications should be stored. Because the list of notifications is meant to grow statically...

Actually not. NeoVim calls this feature floating windows and in Vim they are named popups. Both work in TUI mode (for Vim I assume that).

An example configuration I'm using atm with this branch: ```lua { window = { relative = 'win' size = function(window_number) local window_width = vim.api.nvim_win_get_width(window_number) local width = window_width > minimum_width...

Sorry, currently don't find the resources, but doesn't `nvim-cmp` support inserting parenthesis after the completion by itself?

Okay, it seems like this is a feature of the LSP completion where some servers provide this feature by using snippets. Sorry.

I was actually thinking about exactly such a solution. Probably just need to make it a liiiittle more advanced, so it does not interfere with server which do actually send...

When integrating with the new `vitest list` command, it should be easy and reliable to determine this, right? Because right now, this plugin just hard-codes the default configuration of Vitest...

Hey 👋🏾 Jumping straight into the conversation. Would it be feasible to start with a simple solution where it is possible to run just the "whole" test.each test case? I...

Interesting. Sorry, I haven't thought about the error messages. Very good point. How would this problem of descriptive error message be solved for the very generic approach you proposed? 🤔

Alright, sounds like a good extension to me. :+1: