mirror of
https://github.com/wez/wezterm.git
synced 2024-12-25 22:33:52 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
1e9d3571ba
This is another option to help with the portable wezterm on a flash drive use case. When the font system is set to FontKitAndFreeType, the set of directories specified by the `font_dirs` configuration option will be scanned for fonts and used as a source for fonts. In addition, any relative paths in the the `font_dirs` list will be expanded relative to the configuration file path. That allows deploying the following set of files to the root of a flash drive: * wezterm.exe * wezterm.toml * fonts/myfont.ttf and with this config snippet: ``` font_system = "FontKitAndFreeType" font_dir = ["fonts"] ``` wezterm will now consider myfont.ttf when loading fonts. Refs: https://github.com/wez/wezterm/issues/73 |
||
|---|---|---|
| .cargo | ||
| .github/workflows | ||
| assets | ||
| base91 | ||
| ci | ||
| deps | ||
| docs | ||
| promise | ||
| pty | ||
| src | ||
| tabout | ||
| term | ||
| termwiz | ||
| vtparse | ||
| window | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| azure-pipelines.yml | ||
| build.rs | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| get-deps | ||
| install.sh | ||
| ISSUE_TEMPLATE.md | ||
| 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 gitter room for (potentially!) real time discussions: https://gitter.im/wezterm/Lobby
The 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.