Wez Furlong
Wez Furlong
I'm not suggesting that you have a different problem, I'm just trying to understand why it might be happening; the macOS clipboard API is pretty simple and wezterm hasn't changed...
Elsewhere in wezterm's issue's tagged with wayland there is a discussion about the level of effort involved: the changes from 0.16 -> 0.17 and the wayland ecosystem crates are effectively...
Please try the latest release
Please run: `wezterm ls-fonts --codepoints 1F784` and share the output
Sounds like the same underlying issue as in, where DirectWrite isn't telling us which font to use: * https://github.com/wez/wezterm/issues/4768 the workaround is to explicitly list in your `wezterm.font_with_fallback` list the...
Please try the latest nightly build and let me know if this is still an issue!
My knee-jerk response to this was "no!" because there are challenges with matching text at output time (mostly stemming from the fact that output is not guaranteed to be sequentially...
@rocket-matt this error: ``` 15:14:00.736 ERROR wezterm > failed to exec "/home/matt/.cargo/bin/wezterm-gui": Os { code: 2, kind: NotFound, message: "No such file or directory" }; terminating ``` suggests that you...
Try using the opengl front end; see https://github.com/wez/wezterm/issues/3904#issuecomment-1819571416
The challenge with that is: how do you know from that error message that this is a webgpu problem? It's not obviously connected to the webgpu logic; the `window` crate...