You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am fairly new to NeoVim, but i think I get the main parts right. I played around with nvim-dap and made NodeJS debugging work. Then I tried some frontend stuff with Angular and very soon I stumbled upon the following thing:
While coding I always keep the Angular Dev Server and an instance of Chrome with --remote-debugging-port=9222 running. Whenever I need to debug something I just hit F5 and, no matter where I currently am in the source code, VSCode attaches to the already running debugger of Chrome and I can hit my breakpoints. That's really neat.
This workflow does not work with nvim-dap. Every configuration is associated with a filetype. Maybe I am still missing something or it's a skill issue of some sort, but wouldn't it be great if the above config could just be run with dap.attach() no matter what buffer/file is currently active?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am fairly new to NeoVim, but i think I get the main parts right. I played around with
nvim-dap
and made NodeJS debugging work. Then I tried some frontend stuff with Angular and very soon I stumbled upon the following thing:My launch.json for VSCode look like this:
While coding I always keep the Angular Dev Server and an instance of Chrome with
--remote-debugging-port=9222
running. Whenever I need to debug something I just hit F5 and, no matter where I currently am in the source code, VSCode attaches to the already running debugger of Chrome and I can hit my breakpoints. That's really neat.This workflow does not work with
nvim-dap
. Every configuration is associated with a filetype. Maybe I am still missing something or it's a skill issue of some sort, but wouldn't it be great if the above config could just be run withdap.attach()
no matter what buffer/file is currently active?Beta Was this translation helpful? Give feedback.
All reactions