Fix powershell

[TheLeoP]

Fixes the problems stated in TheLeoP/powershell.nvim#3

Also,

• I couldn't execute your config locally because you weren't calling require('f0oster.packer'), so I fix it
• I updated the listeners for dap-ui (maybe you weren't using the close listeners on purpose(?), you could delete them if that's the case)
• I removed dap-powershell because powershell.nvim already handles debugging and both configurations may clash (or your would only use one of them). dap-powershell does support interactive debugging (through the dap-repl), but it doesn't work on windows (because nvim-dap does not handle named pipes nicely on Windows). powershell.nvim works on Windows (including debugging), but it does not support interactive debugging because of a bug with Powershell Editor Services

[TheLeoP]

Additionally, I haven't use packer since it was archived, so I don't remember exactly how to use it. You may need to :PackerCompile or :PackerSync (or both?) after merging this changes

[f0oster]

@TheLeoP Thanks a lot for your help, I really appreciate it - all seems to be working now. I'm pretty new to neovim and the ecosystem/config is a little confusing so far.

• I couldn't execute your config locally because you weren't calling require('f0oster.packer'), so I fix it

I was typically sourcing packer.lua to run Packer commands, but this change is fine.

• I updated the listeners for dap-ui (maybe you weren't using the close listeners on purpose(?), you could delete them if that's the case)

Thanks for fixing that. I hadn't intentionally configured dap-ui that way - I was just messing about with config last night.

• I removed dap-powershell because powershell.nvim already handles debugging and both configurations may clash (or your would only use one of them). dap-powershell does support interactive debugging (through the dap-repl), but it doesn't work on windows (because nvim-dap does not handle named pipes nicely on Windows). powershell.nvim works on Windows (including debugging), but it does not support interactive debugging because of a bug with Powershell Editor Services

Thanks - I did see this issue last night. I do plan to set this config up on Windows as well, so it's good to know.

Additionally, I haven't use packer since it was archived, so I don't remember exactly how to use it. You may need to :PackerCompile or :PackerSync (or both?) after merging this changes

Yep, I ran a :PackerSync and all is good. Thanks again! You've been a massive help. I'll need to spend a weekend looking at migrating away from Packer and also generally updating my set up some time soon I think.