chtenb

Yes, separators are currently not reasonably usable due to the lacking `inactive` setting. Removing them seems indeed a correct patch until a better set of theming parameters is introduced.

Would this also work for curly underline support in native windows?

I just found that this exact scenario does not work on WSL either, albeit with different symptoms. In WSL on cmd.exe typing unicode in helix just works. In Wezterm however,...

As stated, this issue does not occur in other terminal emulators, just on wezterm.

It's not a font issue as you can see in the screenshot I posted. There isn't much to show about the other terminal emulators. It just works. 

It's not a font problem, because *nothing* is inserted. And on WSL something is inserted, but not a valid single character. If it were a font problem, you would see...

I tried it, it doesn't help. Two other things I noticed: - when turning off allow_win32_input_mode, it also inserts ���� on regular windows, just like on WSL. - On WSL,...

I discovered that the virus scanner on my PC silently messed up the nightly wezterm installer without me noticing. I think that somehow caused the nightly installer to fail silently...

I spoke too soon. It is only fixed for WSL.

Thank you for taking the time to respond! I've configured `default_prog = { 'nu' }`. This is what task manager and procmon show respectively:   Is that helpful, or...