mirror of
https://github.com/wez/wezterm.git
synced 2024-12-23 21:32:13 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
52908712c6
When allocating space in the texture atlas, we typically use a small padding to avoid accidentally interpolating textures into glyphs. When it comes to rendering images via iterm2 or sixel image protocols, the image emitted by the user may not exactly fill the cell dimensions, and due to the how the shader works to apply those textures we could end up revealing nearby images in the texture when displaying an unrelated image. This commit adjusts the texture atlas allocation when making space for image protocol textures; excess padding based on an overestimate of the cell dimensions is added to the right and bottom of the image, guaranteeing that that border will be filled with transparent pixels. This is a bit wasteful of texture space, but isn't egregiously bad and is easy to reason about and makes things look less janky. refs: #292 |
||
|---|---|---|
| .cargo | ||
| .github | ||
| assets | ||
| async_ossl | ||
| base91 | ||
| bintree | ||
| ci | ||
| codec | ||
| config | ||
| deps | ||
| docs | ||
| filedescriptor | ||
| licenses | ||
| luahelper | ||
| mux | ||
| promise | ||
| pty | ||
| rangeset | ||
| ratelim | ||
| strip-ansi-escapes | ||
| tabout | ||
| term | ||
| termwiz | ||
| umask | ||
| vtparse | ||
| wezterm | ||
| wezterm-mux-server | ||
| window | ||
| .cirrus.yml | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| get-deps | ||
| LICENSE.md | ||
| README.md | ||
| wt-record | ||
| wt-replay | ||
Wez's Terminal
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
User facing home page at: https://wezfurlong.org/wezterm/
Screenshot of wezterm on macOS, running vim
Installation
https://wezfurlong.org/wezterm/installation.html
Getting help
This is a spare time project, so please bear with me. There are two channels for support:
- You can use the GitHub issue tracker to see if someone else has a similar issue, or to file a new one: https://github.com/wez/wezterm/issues
- There is a Matrix/Riot.im room for (potentially!) real time discussions; that is bridged from the original Gitter room.
The Matrix/Gitter room is probably better suited to questions than it is to bug reports, but don't be afraid to use whichever you are most comfortable using and we'll work it out.