refactor: make debug functionality better.

[ayamir]

Dap for c/cpp/rust:
We use lldb-vscode to debug, but I found that it doesn't work on my arch wsl2 although I have set the lldb-vscode's path to absolute path, ref: https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#ccrust-via-lldb-vscode
It needs more test on other platforms.
Dap for python:
It works now but needs user install debugpy manually.
ref: https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#Python

[CharlesChiuGit]

Debug for c/cpp/rust can work when using cpptools instead.

I'm considering whether add an installation option for dap adapters like cpptools and debugpy in install.sh and install.ps1. Now I put the executable path in ~/.local/share/nvim/dap/.

cc @Jint-lzxy @CharlesChiuGit

I think that's a gd idea, to save some newcomers from confusing.

[Groveer]

Dap for c/cpp/rust: We use lldb-vscode to debug, but I found that it doesn't work on my arch wsl2 although I have set the lldb-vscode's path to absolute path, ref: https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#ccrust-via-lldb-vscode It needs more test on other platforms. Dap for python: It works now but needs user install debugpy manually. ref: https://github.com/mfussenegger/nvim-dap/wiki/Debug-Adapter-installation#Python

lldb-vscode works for me, and I do't need absolute path, I use env path.

[ayamir]

[aarnphm]

The DAP implementation LGTM. I used to use DAP a lot, not anymore. Still cc others to take a look

[Groveer]

LGTM. It works good for me.

[CharlesChiuGit]

LGTM, but I only tested on python

[Jint-lzxy]

Sorry for the delay. Will test on C++, Objective-C, and Swift.

[Jint-lzxy]

LGTM, currently working on several cleanups like #458 (comment)

[Jint-lzxy]

A small change in wording: Executables with LSP-like capabilities are called "servers", while executables having DAP implementations are called "clients".

• LSP: Language Server Protocol
• DAP: Debug Adapter Protocol

Done

[Jint-lzxy]

LGTM for codelldb and lldb 👍

[Jint-lzxy]

1d9381c implemented a dirty workaround for utils (all parameters passed to the adapter should be functions or tables, and they shouldn't be called during setup):

return setmetatable({}, {
	__index = function(_, key)
		return function()
			return function()
				return M[key]()
			end
		end
	end,
})

Not sure if this is the best way to do so 😢

[ayamir]

We use project.nvim to change cwd automatically, so is it suitable to use vim.fn.getcwd() as default path completion? For example, I have a Cpp-Practices git repo to host my cpp code. Now I enter the directory of a leetcode problem and want to debug the executale. So what I needed is current directory path instead of the workspace path provided by vim.fn.getcwd().

[ayamir]

all parameters passed to the adapter should be functions or tables, and they shouldn't be called during setup

You are right. Previous implementation has the bug about multi-times prompts asking for exe path.

[Jint-lzxy]

We use project.nvim to change cwd automatically, so is it suitable to use vim.fn.getcwd() as default path completion? For example, I have a Cpp-Practices git repo to host my cpp code. Now I enter the directory of a leetcode problem and want to debug the executale. So what I needed is current directory path instead of the workspace path provided by vim.fn.getcwd().

fdb356c

[ayamir]

I think it can be merged now.