Oh-my-posh hiding [DBG] prefix in powershell.

[awa5114]

I am trying to debug a powershell script with Windows Terminal. I have oh-my-posh installed with a customized command prompt. I went through the following steps:

• set-psbreakpoint -script test.ps1 -line 8
• .\test.ps1

I got the following output:

Hit Line breakpoint on 'test.ps1:8'

At test.ps1:8 char:3
+   cat $py_file.fullname
+   ~~~~~~~~~~~~~~~~~~~~~

Which implies that my debugger is working fine. Furthermore I'm able to print out variables from within test.ps1.

Unfortunately, it looks like oh-my-posh is hiding the [DBG] prefix in my command line prompt, which I would like to have.

How can I prevent oh-my-posh from hiding the [DBG] prefix in my command line prompt?

[JanDeDobbeleer]

That's not something we support just yet, but let me see how this works and what needs to be done to enable that.

[mattcargile]

Awesome! Can't wait to try it. I assumed it was some debug context deal. Hopefully we can get this in the repo soon if it is reasonable.

[lewis-yeung]

@mattcargile It's live now. You can try it and if anything is still wrong, just leave a comment.

[JustinGrote]

@lewis-yeung @mattcargile does this still work? I can't seem to get debug_prompt to work correctly, it shows my same prompt when going into debugger.

[mattcargile]

@JustinGrote - It has worked in most contexts, though admittedly I haven't tried it super lately on v12 or later.

I have noticed it breaking depending on how the module is loaded or how one sets the breakpoint like on the command itself versus on a line. I've been meaning to put in an Issue, but I haven't been able to get to it. One needs additional logic on Get-PSCallStack output during various debug contexts, I think.

[JustinGrote]

@mattcargile I recently got a PR merged to handle the other contexts such as ephemeral that weren't working for me. Should be pretty solid now for 99% of use cases.