wez / wezterm

A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
https://wezfurlong.org/wezterm/
Other
16.78k stars 751 forks source link

Fonts are not rendered correctly #651

Closed Sparkenstein closed 3 years ago

Sparkenstein commented 3 years ago

The bug

The fonts are not being rendered correctly, especially the symbols in vim statusline and zsh prompt etc. I compared the output with other terminals, xfce4-terminal and alacritty, it looks fine there. attaching the screenshot below:

Environment (please complete the following information):

To Reproduce

Try any patched nerd font with status-line in vim or simply try p10k.zsh if you are using ZSH, no need to change any configuration, the behavior is observed on default settings as well

Configuration

PS: trimmed few unnecessary keybindings about window/panes management table.insert(mykeys...) etc let me know if you need full config

local wezterm = require 'wezterm';

local mykeys = {}
for i = 1, 9 do
    table.insert(mykeys, {
        key=tostring(i),
        mods="CTRL|SHIFT",
        action=wezterm.action{ActivateTab=i-1},
    })

    table.insert(mykeys, {
        key="F" .. tostring(i),
        action=wezterm.action{ActivateTab=i-1},
    })

end

return {
  -- Fonts
  font = wezterm.font("MesloLGS NF"),
  font_size = 15.0,
  line_height = 1.2,

  -- Colors
  bold_brightens_ansi_colors = true,
  inactive_pane_hsb = {
        hue = 1.0,
        saturation = 0.7,
        brightness = 0.6,
  },
  -- UI
  color_scheme = "Galaxy",

  -- Keybindings
  leader = { key = "m", mods="CTRL" },
  keys = mykeys,

}

Screenshots

issue

Note the left one is wezterm, right top is xfce4-terminal, right bottom is alacritty,

Sparkenstein commented 3 years ago

Hmm, now that I have looked closely, even alacritty is not rendering it properly, there's small misalignment on second line on right prompt

wez commented 3 years ago

Seems like the same underlying issue as #584 which has a draft PR: #588 Possibly also related to #614

wez commented 3 years ago

Duplicate of #584

github-actions[bot] commented 1 year ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.