oli/nvim
1
1
Fork 0
Code Issues Pull Requests 1 Releases 1 Wiki Activity

first running verion of dab python

Browse Source
This commit is contained in:
Oliver Hartmann 2022-08-06 15:26:18 +02:00
parent 69b5cace69
commit 49f8494072
2 changed files with 37 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored
View File

@ -5,3 +5,4 @@ vim.bundle
plugged
rplugin.vim
plugin/packer_compiled.lua
venv_debugpy

66
lua/setup/my_dap.lua
View File

@ -10,35 +10,41 @@ vim.keymap.set('n', '<S-F11>', ":lua require('dap').step_out()<CR>", opts)
-- vim.keymap.set('n', '<F11>', dap.step_into(), opts)
-- vim.keymap.set('n', '<S-F11>', dap.step_out(), opts)
dap.adapters.python = {
type = 'executable';
command = 'C:/Users/oli/AppData/Local/nvim-data/mason/packages/debugpy/venv/Scripts/python.exe';
args = { '-m', 'debugpy.adapter' };
}
dap.configurations.python = {
{
-- The first three options are required by nvim-dap
type = 'python'; -- the type here established the link to the adapter definition: `dap.adapters.python`
request = 'launch';
name = "Launch file";
-- Options below are for debugpy, see https://github.com/microsoft/debugpy/wiki/Debug-configuration-settings for supported options
program = "${file}"; -- This configuration will launch the current file if used.
pythonPath = function()
-- debugpy supports launching an application with a different interpreter then the one used to launch debugpy itself.
-- The code below looks for a `venv` or `.venv` folder in the current directly and uses the python within.
-- You could adapt this - to for example use the `VIRTUAL_ENV` environment variable.
local cwd = vim.fn.getcwd()
if vim.fn.executable(cwd .. '/venv/bin/python') == 1 then
return cwd .. '/venv/bin/python'
elseif vim.fn.executable(cwd .. '/.venv/bin/python') == 1 then
return cwd .. '/.venv/bin/python'
else
return '/usr/bin/python'
end
end;
},
}
-- dap.adapters.python = {
-- type = 'executable';
-- command = 'C:\\Users\\oli\\AppData\\Local\\nvim\\venv_debugpy\\Scripts\\python';
-- args = { '-m', 'debugpy.adapter' };
-- options = {
-- detached = true;
-- };
-- }
-- dap.configurations.python = {
-- {
-- -- The first three options are required by nvim-dap
-- type = 'python'; -- the type here established the link to the adapter definition: `dap.adapters.python`
-- request = 'launch';
-- name = "Launch file";
--
-- -- Options below are for debugpy, see https://github.com/microsoft/debugpy/wiki/Debug-configuration-settings for supported options
--
-- program = "${file}"; -- This configuration will launch the current file if used.
-- pythonPath = function()
-- -- debugpy supports launching an application with a different interpreter then the one used to launch debugpy itself.
-- -- The code below looks for a `venv` or `.venv` folder in the current directly and uses the python within.
-- -- You could adapt this - to for example use the `VIRTUAL_ENV` environment variable.
-- local venv = os.getenv("VIRTUAL_ENV")
-- return string.format("%s\\bin\\python.exe",venv)
-- -- local cwd = vim.fn.getcwd()
-- -- if vim.fn.executable(cwd .. '/venv/bin/python') == 1 then
-- -- return cwd .. '/venv/bin/python'
-- -- elseif vim.fn.executable(cwd .. '/.venv/bin/python') == 1 then
-- -- return cwd .. '/.venv/bin/python'
-- -- else
-- -- return '/usr/bin/python'
-- -- end
-- end;
-- },
-- }
require('dap-python').setup('C:\\Users\\oli\\AppData\\Local\\nvim\\venv_debugpy\\Scripts\\python')
-- require('dap-python').setup('C:/Users/oli/AppData/Local/nvim-data/mason/packages/debugpy/venv/Scripts/python.exe')