Console - Oh-My-Posh/Windows Terminal font support

Hello,

Thank you for reaching out to us regarding this,

Could you please specify the version of RDM you are currently using?
What type of data source are you using?

Let me know,

Best regards,

I'm using the latest version available from the website: 2024.3.27.0 64-bit on .NET 8.0.12.

I had previously overwritten the font manually under Settings>Entry types>Sessions>Terminal>Terminal font with Cascadia Code NF (installed through OMP) but I have disabled it and I observe the same behaviour.


As for the Data Source: I'm just running this on a Local one with no customizations on it.

Furthermore, I notice that there's a brief error flashing on the screen before giving me a cursor, and I can see the following with Get-Error. I found that these are related to the "buffer" for the PowerShell session. Not sure if it's related:

Hi,

Can you try installing the Devolutions Windows Terminal distribution separately from Remote Desktop Manager to see if you have the same issue with it?

https://github.com/devolutions/wt-distro
https://github.com/Devolutions/wt-distro/releases/tag/v1.20.11271.0

Unlike the official MSIX distribution, ours will store settings.json under "%LocalAppData%/Microsoft/Windows Terminal". If you can configure your profile such that we can try to reproduce the issue on our side, I would appreciate a copy of the resulting settings.json to help investigate this further.

Best regards,

I was completely unaware that there was a dedicated version to address this! I have installed it and it works as a standalone item:


But when I try to set it up on RDM, there's only ONE "Windows Terminal" entry and the drop down is empty when I try to select something:


The resulting terminal after installing the Devolutions version still renders the glyphs incorrectly. I've also attached the settings.json for reference.

I have installed oh-my-posh and tried loading it it in RDM, I don't seem to be hitting the same problem you do. We do inject a few commands inside the new terminal to resize it such that it fits within RDM, you can see what the command is with the "Debug" checkbox. Try disabling the "Resize window" and play with the "No profile" option, maybe you'll be able to figure out what it does differently than Windows Terminal outside of Remote Desktop Manager.

Apologies for the massive delay! Just returned from overseas - Did not have my laptop and was not able to test/reply on this topic. The issue that I had was that I was using a "Powershell Terminal" session type instead of a "Windows Terminal" one. Once I noticed this - it was all working fine with OMP.

Quick question - what's the difference between the two of these terminal types? I am thinking they are loading different processes in the background.

Hello,

Thank you for your reply,

For your question, you would be correct; for the Powershell entry using Windows terminal mode, we are starting a powershell.exe process using windowsterminal.exe, while for a Windows Terminal entry, it is simply launching windowsterminal.exe.

Let me know if this answers your question,

Best regards,