vim-test VS nvim-dap-python

If you need inspiration, you can use vim-test as a reference. It's the Vim equivalent of neotest, written in Vimscript (doesn't support tree-sitter and diagnostics).

My plugin NeoTerm.lua supports "run test at cursor" out of the box with vim-test, i.e. zero configuration.

Vim test is great, supports a lot of frameworks and is easy to extend (with vi script) https://github.com/vim-test/vim-test

I am trying to set up the popular vim-test (https://github.com/vim-test/vim-test) plugin so that when I run tests they run on a tmux pane. vim-test uses a default strategy of running the tests via neovim’s built-in terminal. They also support many strategies which include running on a tmux pane.

I use https://github.com/vim-test/vim-test runs tests in a lot of languages. Very fast and clean output.

vim-test run your test with a simple mapping. Works with rSpec and Minitest (and dozens other languages)

I've made the move from vim to Emacs with Evil-mode for a little while now, but still miss https://github.com/vim-test/vim-test. I wonder if there's a port for evil-mode or if you know of something closer to it you can recommend. Thanks

One project that does a fantastic job on these two points is https://github.com/vim-test/vim-test Both adding new execution environments and test-runners can be done with minimal fuzz. Only thing is I would like a tutorial of how to add a new runner.

I think nvim-dap doesn't (always?) use neovim current working directory as root, which can cause issues like yours. I'd recommend using https://github.com/mfussenegger/nvim-dap-python along with a local .nvim.lua (:h 'exrc') with the following config:

You could use nvim-dap with nvim-dap-python.

I'd suggest starting with a Neovim distro that makes things work for you and as you get familiar you can transition to a more custom configuration as you see fit. If you want to do it by yourself then the most popular plugin for debugging in Neovim is nvim-dap and there is also an extension for Python to give you a more ready to go config instead of doing it yourself. You should read the docs of those 2 to see how you should customize accordingly your configuration.

I figured out a solution btw. I got this plugin and created a .vscode/launch.json file for my project and set the cwd in there

lmao. I'm asking this because I'm trying to do this. Just want to know whether this is a good idea. I have some basic setup using nvim-dap-python.

-- Debug adapter plug-in. Debug anything in Neovim { "mfussenegger/nvim-dap", config = function() vim.keymap.set("n", "d", ":DapContinue") vim.keymap.set("n", "dl", ":DapStepInto") vim.keymap.set("n", "dj", ":DapStepOver") vim.keymap.set("n", "dh", ":DapStepOut") vim.keymap.set("n", "dz", ":ZoomWinTabToggle") vim.keymap.set( "n", "dgt", -- dg as in debu[g] [t]race ":lua require('dap').set_log_level('TRACE')" ) vim.keymap.set( "n", "dge", -- dg as in debu[g] [e]dit function() vim.cmd(":edit " .. vim.fn.stdpath('cache') .. "/dap.log") end ) vim.keymap.set("n", "", ":DapStepOut") vim.keymap.set("n", "", ":DapStepOver") vim.keymap.set("n", "", ":DapStepInto") vim.keymap.set( "n", "d-", function() require("dap").restart() end ) vim.keymap.set( "n", "d_", function() require("dap").terminate() require("dapui").close() end ) end, lazy = true, }, -- A default "GUI" front-end for nvim-dap { "rcarriga/nvim-dap-ui", config = function() require("dapui").setup() -- Note: Added this dd duplicate of because somehow the -- mapping keeps getting reset each time I restart nvim-dap. Annoying but whatever. -- vim.keymap.set( "n", "dd", function() require("dapui").open() -- Requires nvim-dap-ui vim.cmd[[DapContinue]] -- Important: This will lazy-load nvim-dap end ) end, dependencies = { "mfussenegger/nvim-dap", "mfussenegger/nvim-dap-python", -- Optional adapter for Python }, }, -- TODO: Make sure that debugpy is installed. Otherwise, disable -- Reference: https://github.com/mfussenegger/nvim-dap-python#installation -- { "mfussenegger/nvim-dap-python", config = function() require("dap-python").setup("/path/to/python/here") -- XXX: Replace this with your preferred Python, if wanted -- An example configuration to launch any Python file, via Houdini -- table.insert( -- require("dap").configurations.python, -- { -- type = "python", -- request = "launch", -- name = "Launch Via hython", -- program = "${file}", -- python = "/opt/hfs19.5.569/bin/hython" -- -- ... more options, see https://github.com/microsoft/debugpy/wiki/Debug-configuration-settings -- } -- ) end, dependencies = { "mfussenegger/nvim-dap", "nvim-treesitter/nvim-treesitter", }, }, -- Remember nvim-dap breakpoints between sessions, ``:PBToggleBreakpoint`` { "Weissle/persistent-breakpoints.nvim", config = function() require("persistent-breakpoints").setup{ load_breakpoints_event = { "BufReadPost" } } vim.keymap.set("n", "db", ":PBToggleBreakpoint") end, }

Oh yes.. I think https://github.com/mfussenegger/nvim-dap-python is what you are looking for. The configuration might not be as simple as the VS code equivalent but seems to serve the same purpose?

But how do specify the same virtual env for Debugging with dap? nvim-dap-python is looking for the env variables VIRTUAL_ENV and CONDA_PREFIX. But that means i cannot open multiple python projects in the same nvim instance.

Yes, you can use nvim-dap-ui on top of nvim-dap or just nvim-dap-python (note that I haven‘t used the latter). Both options are able to parse .vscode/launch.json debug configs.

Have you installed and configured nvim-dap and nvim-dap-python ?