zoumi

RAlt ``` VK SC Up/Dn Key ------------------------------------------------------------------------------------------------------------- A5 138 d RAlt A5 138 u RAlt ``` LAlt ``` VK SC Up/Dn Key ------------------------------------------------------------------------------------------------------------- A4 038 d LAlt A4 038 u...

Yes,it works now.Thank you!

I have renamed clangd to clangd_ori.exe to get trace info. And the content of compile_command.json is wrong, but I think it should not crash clangd.

The situation is a little complicated. This only happen when I open two project dirs in gvim. The other dir is not reside in esp-idf dir. Where can I get...

Why not create a PR?

By the way, the file's path show in the window title is strange. before you press Ctrl-] the the file path is `C:\xxx\xxxx\xxxx.c` first time you press Ctrl-] the file...

The bug is at /plat/win32/update_tags.cmd when it is parsing args: -e "ctags" -t "C:\Users\zoumi\.cache\tags\E--Program_Files_(x86)-Vim-tags" -p "E:\Program Files (x86)\Vim" -o "E:\Program Files (x86)\Vim\vimfiles\bundle\vim-gutentags\res\ctags_recursive.options" -O "--output-format=e-ctags" -l "C:\Users\zoumi\.cache\tags\E--Program_Files_(x86)-Vim-tags.log" it get the error....

There is another bug?: In my case, tag file should be "C:\Users\zoumi.cache\tags\E--Program_Files_(x86)-Vim-\tags" not "C:\Users\zoumi.cache\tags\E--Program_Files_(x86)-Vim-tags"

For example: When user call \:VimspectorPause when the program is running in libc.so, and this libc.so contains debug info, but the debug info point to a source file path that...

more debug msg: ``` zoumi@zoumi-PC MINGW64 /h/work/rust_projects/com_tool (master) $ /e/rustdir/target/debug/ComTool.exe "D:\\zh-WORK\\rust\\com_tool" [15:46:09] INFO The application is starting... [15:46:09] INFO Application's working dir is :"H:\\work\\rust_projects\\com_tool" [15:46:09] DEBUG "http://127.0.0.1:24050/com_tool.html" [15:46:09] DEBUG Server...