Extra space in some console when using surrogate pair

[sharky98]

Code of Conduct

• I agree to follow this project's Code of Conduct

What happened?

When I use a surrogate pair (such as \udb80\udced for the nf-md-calendar icon), there is sometime (see note) an extra space before the trailing diamond and after the content of the segment that does not get styled.

Note: It depends of the combination of shell (pwsh or bash via SSH) and program (VSCode, Windows Terminal, Tabby)

Theme

I am using a custom theme derived from night-owl. The relevant segment for the above screenshot is this.

{
  "blocks": [
      "segments": [
        {
          "background": "#234d70",
          "foreground": "#d6deeb",
          "leading_diamond": "<transparent,background>\ue0b0</>",
          "properties": {
            "time_format": "2006-01-02"
          },
          "style": "diamond",
          "template": " \udb80\udced {{ .CurrentDate | date .Format }} ",
          "trailing_diamond": "<background,transparent>\ue0b0</>",
          "type": "time"
        },
    ]
  ]
}

What OS are you seeing the problem on?

Windows, Linux

Which shell are you using?

bash, powershell, other (please specify)

Log output

• Windows Terminal
  • ✅ pwsh.exe: omp.pwsh.terminal.log
  • ✅ bash through SSH: omp.bash.terminal.log
• Tabby
  • ❌ pwsh.exe: omp.pwsh.tabby.log
    
  • ✅ bash through SSH: omp.bash.tabby.log
    
• VS Code
  • ❌ pwsh.exe: omp.pwsh.vscode.log
    
  • ❌ bash through SSH (in pwsh.exe): omp.bash.vscode.log
    
• Console Host:
  • ✅ pwsh.exe: omp.pwsh.conhost.log
    

[JanDeDobbeleer]

@sharky98 unfortunately, this is a terminal bug and not an oh-my-posh one.

[sharky98]

@sharky98 unfortunately, this is a terminal bug and not an oh-my-posh one.

This is what I though, but since in Tabby the behaviour was different between pwsh and bash, I was thinking it may be due to oh-my-posh.

Thanks! 🙂

[github-actions]

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues.
If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.