Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

neotest only discovers positions for new buffers after writing a file #208

Closed
mrcjkb opened this issue Feb 3, 2024 · 1 comment · Fixed by #223
Closed

neotest only discovers positions for new buffers after writing a file #208

mrcjkb opened this issue Feb 3, 2024 · 1 comment · Fixed by #223
Labels
bug Something isn't working upstream

Comments

@mrcjkb
Copy link
Owner

mrcjkb commented Feb 3, 2024

To reproduce:

:e foo.rs
:Neotest run "runs tests for the current file
:e bar.rs
:Neotest run "No positions found
:w
:Neotest run "runs tests for the current file

This is likely because rustaceanvim only sends LSP client requests for buffers to which there's a client attached.

Possible solutions:

  • Query all files, using the first client with a maching workspace root [a first attempt at this was not successful]
  • Add an autocmd to rediscover positions on BufEnter
@mrcjkb mrcjkb added bug Something isn't working upstream labels Feb 3, 2024
@mrcjkb
Copy link
Owner Author

mrcjkb commented Feb 3, 2024

nvim-neotest/neotest#360

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant