9 ms·
WezTerm is a GPU-accelerated cross-platform terminal emulator written in Rust
- einpoklum 4y agoNot a criticism of this app itself, but - I could not find an explanation on the website why I would prefer this terminal emulator & multiplexer to those available with every desktop environment, such as gnome-terminal, lxterminal, qterminal, xfce4-terminal etc.
- deleted 4y ago[deleted]
- kitsunesoba 4y agoWezTerm seems nice in a lot of ways, but it's got some odd quirks, like how it lacks menus on macOS or how on Linux, it uses a hyperminimalist tiling-WM-style titlebar instead of whatever your WM furnishes. This makes it seem pretty squarely targeted at i3/Sway/vim sorts of users, which doesn't make it bad but an odd fit for more general users.
- anta40 4y agoI tried WezTerm for a few months on MacOS. No problem so far (my use case is pretty minimal, e.g tab 1 for compiling, tab 2 for code editing, tab 3 for SSH, etc), except lacking of GUI for user configuration. You need to understand Lua for that: https://wezfurlong.org/wezterm/config/files.html https://wezfurlong.org/wezterm/config/files.html Eventually I uninstalled it and back to iTerm2. Maybe one day I'll learn Lua and use it again.
- pohl 4y agoI installed the nightly version yesterday, and was pleased to see menus On macOS.
- dmytrish 4y agoI feel like WezTerm has a vision of being something bigger than a traditional VT emulator. It feels more like an environment to live in, an Emacs of terminal emulators, with its own tiling, status bar, dynamic scripting, builin Lua console, programmable events, very rich graphics. It's not a faithful old-school TTY emulator like xterm, it's not featureful, but boring Konsole, it's not ascetic but fast Alacritty. It's an experiment. I don't personally like all of its design decisions, but an Emacs-like vibe really intrigues and attracts me.
- SaintSeiya84 4y agoIn what something is written is irrelevant, please stop with this "written in Rust" as it is not an automatic badge of quality. if you have to specify that something is written in any language (Rust the latest trend) then it has no merits on its own.
- DannyBee 4y agoIt is also unlikely, being a GPU based terminal, that it is written without lots of unsafe memory munging and other fun things, since the underlying API's are still C/C++, and even if they aren't, interacting with GPUs and other hardware is just hard sometimes if they haven't been built thinking of your programming of language. There is of course, a difference between wrapping C apis and them being automatically unsafe, and using lots of unsafe rust like memory transmutation/etc. In the case of wezterm, a quick glance shows that not only is this correct (lots of unsafe rust, even beyond the normal use of wrapped functions), there is also not a lot of documentation about what the safety conditions of the various unsafe code is. (which is the usual good practice in handling this sort of thing). So to your point, saying it's "written in rust" doesn't matter here.
- einpoklum 4y ago> since the underlying API's are still C/C++, If the use of GPUs is via CUDA, there are my wrappers [1] which are RAII/CADRe, and therefore less unsafe. And on the Rust side - don't you need a bunch of unsafe code in the library enabling GPU support? [1] : https://github.com/eyalroz/cuda-api-wrappers/ https://github.com/eyalroz/cuda-api-wrappers/
- DannyBee 4y agoYou do, but people here really don't like to admit the rust ecosystem is like that. There is plenty of code that is infinitely better and safer than the equivalent C++ would ever be. There is lots of "bad" unsafe code that is much worse, and over time, they will have just as much trouble trying to handle this overall as C++ does. (and no the ability to say you don't want unsafe transitive crates doesn't fix anything)
- ama5322 4y agoOn my machine, when I last tried the various accelerated terminal emulators, I wasn't convinced. At least under plain X, GL context creation adds extra latency when creating new windows (might be different if you use a compositor all the time I guess). In addition, on terminals such as kitty, the startup time of a full new process was really non-negligible I suspect due to the python support. With a tiling window manager, the built-in notebook/tiling functionality is not really useful (the window manager is more flexible and has universal keybindings) so when looking at the time required to pop a full new window in either single or shared instance they were actually behind regular xterm. Resource usage wasn't stellar either (xterm was still better than most lightweight libvt-based terminals). Couldn't feel much of a latency improvement (again, X without compositor). I'm sure at full throughput the difference is there, but who is looking at pages of output you can't read? I do keep terminals open for days, but my most common usage case is mostly open window -> run a small session -> close and I got annoyed fast.
- zadjii 4y agoIn my experience, there's two archetypes of terminal users: * Open one window and leave it open forever. Reuse that one for all commands. * Open a window, run a couple commands, and close it. For the second group, startup perf is everything, because users hit that multiple times a day. For the first group, not so much. Some of the other tiling functionality is also more helpful for folks that aren't on platforms with as powerful of window managers (macOS, Windows)
- badsectoracula 4y agoI am in the second group, kinda - i hit Win+Shift+X (my global key for opening a new terminal) pretty much all the time to enter a few commands. I basically open terminals in a "train of thought"-like fashion, when i think of something that isn't about what i do in one terminal i open another to run/check/etc out. Sometimes i even close those terminals too :-P (when i work on something there might be several terminal windows scattered all over the place in different virtual desktops). Also i'm using xterm and i always found it very fast, i never thought that i'd like a faster terminal.
- 4y ago
- deleted 4y ago[deleted]
- realworldperson 4y ago[dead]
- rjzzleep 4y agoDoes anyone know the impact on battery compared to alacritty and kitty?
- benfrain 4y agoAs a Neovim user I like that the config is in Lua. There are however odd things that it still doesn’t have compared to Kitty, like the ability to have squared off corners in macOS
- imran-iq 4y agoThe killer feature of kitty for me is `crtl-shift-e`[0]. I really wish more emulators would copy it. Wezterm has explicit hyperlinks[1], but it requires you to click it with a mouse which is the last thing I want to do when inside a terminal. -- 0: https://sw.kovidgoyal.net/kitty/conf/#shortcut-kitty.Open-URL https://sw.kovidgoyal.net/kitty/conf/#shortcut-kitty.Open-UR... 1: https://wezfurlong.org/wezterm/hyperlinks.html#explicit-hyperlinks https://wezfurlong.org/wezterm/hyperlinks.html#explicit-hype...
- ivolimmen 4y agoFor me the starting reason was the speed of the terminal but now its the open last command output in less[0], I know no other terminal that does this and it is a true life saver. 0: https://sw.kovidgoyal.net/kitty/conf/#shortcut-kitty.Browse-output-of-the-last-shell-command-in-pager https://sw.kovidgoyal.net/kitty/conf/#shortcut-kitty.Browse-...
- mkhnews 4y agoI used wezterm for a while and we added this key binding, I think it was from Wez himself ? - { key="e", mods="CTRL|ALT", action=wezterm.action{QuickSelectArgs={ patterns={ "http?://\\S+", "https?://\\S+" }, action = wezterm.action_callback(function(window, pane) local url = window:get_selection_text_for_pane(pane) wezterm.open_with(url) end) } } },
- eviks 4y agois there a way to make this work with Explicit Hyperlinks?
- 4y ago
- MuffinFlavored 4y agoSerious question: why does a terminal editor need GPU acceleration? It's usually showing 80x25 of text, yeah? I guess text can get scrolling quickly sometimes or it needs maybe... 1,000,000 lines of lookback
- s9w 4y ago[dead]
- yjftsjthsd-h 4y ago> It's usually showing 80x25 of text, yeah? That would be pretty small in modern times. Certainly some people are working with terminals that size, often then spilling out into multiple terminals side by side on the screen, but modern resolutions are good enough to support a lot more text per terminal than that. As a single data point, my half-screen terminal right now is 140x75.
- SauciestGNU 4y agoAnother data point, I keep a 1920x1200 monitor in portrait mode and have kitty fullscreen on that monitor. My workflow is [emacs, browser] + kitty, I keep emacs and my browsers fullscreen on another monitor.
- linsomniac 4y agoA couple of points: - WezTerm has windows/tabs/panes in it, and one use case would be ~10 panes on a 4K display in various columns/rows. - Within those you might have applications that themselves have columns/rows of panes, like vim. - Why not use the GPU to draw the graphics so you can offload the CPU? When there's a lot of text to go through (something scrolling stdout hard, jumping through a big file), the extra performance can be nice.
- NikkiA 4y agoWhy do you think pixels constituting text are any different to pixels constituting images? A terminal editor needs GPU acceleration for the same reasons any other displayed item needs GPU acceleration.
- linsomniac 4y agoBeen using WezTerm as my primary term for ~6 months and been loving it. In particular: - Keyboard cut-and-paste. CtlShiftSpace to highlight likely selections, matching letter to cut, shift letter to cut AND paste. - Built in mosh+tmux-like functionality, but at the GUI level. I do a lot of terminal work at home from my Mac connected to my Linux laptop WezTerm instance, with multiple panes/tabs.
- betaby 4y agoOSC52 support is a major plus for me, another one with OSC52 support is alacritty
- feiss 4y agoI've been using it for +1 year now, love it. I have only one complain: I tried everything to configure it to open in a specific position in the screen (top left corner), and for FSM's sake, It's impossible! (Windows 10)
- eviks 4y agoit's possible now with the nightly version (might need negative X on some machines) local wezterm = require("wezterm") wezterm.on('gui-startup', function(cmd) -- set startup Window position local tab, pane, window = wezterm.mux.spawn_window(cmd or {position={x=0,y=0},width=100,height=20} ) end)
- feiss 4y agoOh, I will try, thanks so much!
- tngranados 4y agoI switched to WezTerm a few months ago after setting up a new computer and missing an easy way to share the iTerm2 config between my computers just like I do with most of my other tools that use dotfiles. It’s a very nice application, easy to configure, very customisable, stable. I’ve only have experienced one bug with app, I opened an issue in GH and Wez had a nightly version with a fix in just a few hours. If you haven’t check it out yet, I highly recommend it.
- deleted 4y ago[deleted]
- volkadav 4y agoWez is a really nice guy to work with too; had the pleasure of working with him briefly a bit over a decade ago (we were at sort of sister companies on a project that involved both). Sadly he was impacted by the layoffs at Meta recently, so if you're looking for an incredibly productive and sharp as hell engineer, it might be worth looking him up.
- bsnnkv 4y agoAfter reading the comments on this thread I decided to give wezterm a try today. It's safe to say that I probably won't be going back to kitty or alacritty any time soon! Such a pleasant experience to configure with lots of very sane defaults. The only things I added were the open-http-links-in-browser binding I found in the comments here, and a quick select matcher for sha256-* strings for when I'm updating manually packaged things in my Nix config.
- 355E3B 4y agoIf you’re on MacOS with a newer device, make sure to set front_end = “WebGpu” in your wezterm.lua file, so Wezterm can utilize Metal drivers. I spent ages trying to get Wezterm font rendering to match iTerm2. After spending far too long in the font section of configuration, it turns out this was the solution.
- deleted 4y ago[deleted]
- ptnxlo 4y agoI've been using WezTerm for a year more or less and haven't had any problems so far. Whenever I want anything fancy I just go to the docs or dig through the Github repo (issues, PRs, etc) and that's all I need. I just couldn't stand the petulant attitude of Alacritty's maintaner(s) and it didn't take much to find something else. Although I can't give this for granted now I haven't seen there's the same sort of behavior on WezTerm.
- snvzz 4y agoI'd be interested in latency measurements. I can't care less about the throughput of a terminal; xterm was fast enough 20 years ago.
- yuryk 4y agoBest terminal for MacOS.
- quag 4y agoI really wanted WezTerm to be the best terminal on macOS. However, when I tried switching from Kitty to WezTerm a month or so ago I found WezTerm’s latency was noticeably higher than Kitty and WezTerm often painted lines as blank in vim when they actually had content. So I was forced to go back to Kitty on macOS. On Linux, it’s no contest, I love WezTerm over Kitty on Linux and didn’t have any of these issues.
- mattrighetti 4y agoWhat does this have to offer compared to Alacritty?
- arusahni 4y agoAs someone who doesn't use tmux, two features pushed me to this over Alacritty: native scrollback with a scrollbar, and native tabs.
- dmytrish 4y agoTabs, splits, programmability, best-in-class graphics support, an ssh multiplexor, session management, Lua scripting. Alacritty and Wezterm have very different--if not opposite--philosophies. Choose Alacritty if you want something simple, fast, focused, done right. Choose WezTerm for flexibility and being a cross-platform environment by itself.
- lwhsiao 4y agoLigatures is one. I also find the copy mode and the hyperlinks feature [1] handy. [1]: https://wezfurlong.org/wezterm/hyperlinks.html https://wezfurlong.org/wezterm/hyperlinks.html
- halfdan 4y agoMain thing was support for ligatures which Alacritty does not support: https://github.com/alacritty/alacritty/issues/50 https://github.com/alacritty/alacritty/issues/50
- Kukumber 4y ago145mb-226mb for a terminal that's worse than an electron terminal something is wrong
- kristjansson 4y agoLooks like the macOS binary size is a combination of shipping 3 binaries, each with most of the application compiled in (and statically linked), and containing builds for both Apple Silicon and x86 in each. 2 % tree . . └── Contents ├── Info.plist ├── MacOS │ ├── strip-ansi-escapes │ ├── wezterm │ ├── wezterm-gui │ └── wezterm-mux-server ├── Resources │ ├── terminal.icns │ └── wezterm.sh └── _CodeSignature └── CodeResources 2 % du -hs Contents/MacOS/* 2.8M Contents/MacOS/strip-ansi-escapes 48M Contents/MacOS/wezterm 119M Contents/MacOS/wezterm-gui 44M Contents/MacOS/wezterm-mux-server A bit of duplicative bloat, but there's nothing wrong with that for an young project trading a bit of space for an easier build/release process.
- _gabe_ 4y agoThis does seem crazy. I have a hobby project that's a statically linked animation editor (so it does a lot of stuff including exporting/encoding GPU streams into a video). It has AV1, Freetype, and a few other large deps included and it only clocks in at 16.7mb
- i_love_cookies 4y ago[dead]
- jeroenhd 4y agoRust has the NodeJS/Python dependency tree bloat problem. Unlike other terminal emulators, this project is entirely statically compiled, so the code for the built-in SSH client, serial port support, muxing server/client protocol, shader compilation engines, image decoding libraries, D-BUS clients, threading libraries, HTTP(S) (1.1/2/3) with several types of compression, and of course the GPU shader compilers and APIs. I built Wezterm on my machine and the binary is about 21MiB in size. About 12MB of that is code, the rest is debug symbols. 2MB of that is the Rust standard library and another 1MB is a LUA runtime. Then there are several image libraries that take about half a megabyte. The compiled source code itself is only 893KiB in my file. The rest is just dependencies and random ELF segments. So yes, the terminal emulator is about one Windows 95 installation in size, but that's all quite explainable if you care about the features. For comparison, I've run `debtree` on gnome-terminal (3.4KiB on disk) and the dependency tree is reported to be 691MiB. Microsoft's Windows Terminal is distributed in 18.6MiB - 66.4MiB (I don't know the compression msixbundles use if any) which is comparable. iTerm2 seems to be about 74MiB decompressed. Even `xterm` (the most barebones terminal emulator I can find) relies on 20MiB of dependencies. If xterm is all you need, then there's no need to download anything else. If you want more features in a terminal emulator, you're going to have to deal with larger binaries.
- baggiponte 4y agowhat's the difference with alacritty?
- eviks 4y agotabs, ligatures and much more flexible configuration with its lua configs
- yohannesk 4y agoI am guessing multiplexer. I really miss tmux on windows, hopefully this could be a replacement. But I don't know about the project
- zadjii 4y agoFWIW the Windows Terminal also natively supports panes & tabs for multiplexing: https://learn.microsoft.com/en-us/windows/terminal/panes https://learn.microsoft.com/en-us/windows/terminal/panes which were highly inspired by tmux.
- cubancigar11 4y agoI live inside tmux inside alacritty running wsl. I tried wezterm after reading all the great reviews last time it was posted on hacker news and i found it severely lacking in font configuration department contrary to popular opinion here.
- michaelsbradley 4y agokitty is also worth a look, though it doesn't run on Windows: https://sw.kovidgoyal.net/kitty/ https://sw.kovidgoyal.net/kitty/ https://github.com/kovidgoyal/kitty/releases https://github.com/kovidgoyal/kitty/releases I used iTerm2 on macOS for many years and still keep it around, but switched to kitty as my daily driver in late 2021 and have been very happy with it.
- malkosta 4y agome too...kitty got me out of iterm2, it feels more responsive, faster to close and open new windows/tags
- codetrotter 4y agoNot to be confused with KiTTY http://www.9bis.net/kitty/index.html#!index.md http://www.9bis.net/kitty/index.html#!index.md > KiTTY is a fork from version 0.76 of PuTTY > KiTTY is only designed for the Microsoft® Windows® platform.
- metal_am 4y agoHonest question: for someone who doesn’t live in a terminal, what does something like this do that a default terminal with OhMyZsh doesn’t do?
- kzrdude 4y agoWezterm for example supports various protocols for images in a terminal. Many do, but some standard terminals don't. Gnome-terminal still doesn't. Terminal.app in MacOs doesn't.
- gleenn 4y agoZsh is the shell which is a mini language and environment, so you can run that in many different terminals. OhMyZsh is a set of configuration scripts and plugins to configure Zsh. A terminal is the thing that renders text, handles input and all the escaping complexities. So it's usually the UI/colors around the text that the shell provides. Old terminals were even physical devices with ports that allowed connecting to headless computers.
- epage 4y agoBeen digging into escape sequences lately and gave WezTerm a spin to test some things out One thing that put a sour taste in my mouth for WezTerm is they document all escape sequences [0] using a deviation from standard syntax (sometimes using `:` over `;` like for RGB colors, at least I've not found any other documentation about this being commonly adopted). They do put a disclaimer at one point in the document but that only helps if you read it linearly and it feels weird to document your implementation of a standard to only work with your terminal, locking people's applications into it. As for rendering, I had problems with what look like correct escape sequences not rendering correctly (alternative underline styles, colored underlines). I still need to dig further into this where in the stack the problem is (my application or where in WezTerm) [0] https://wezfurlong.org/wezterm/escape-sequences.html https://wezfurlong.org/wezterm/escape-sequences.html
- drougge 4y agoColon is the correct separator there. Semicolon separates different instructions, a group of values that is a single instruction is colon separated. For example \e[38:5:196;1m specifies red and bold. Using ";" is popular, and some parsers even require it, but it makes little sense. A terminal that doesn't know about 38 (anything old) will interpret that 5 as blink if you use ";", which is not what anyone wants.
- zadjii 4y agoFrom my experience, the colon separator for 256/rgb attributes is a fairly recent clarification to the spec. I think that's the way it was always supposed to be. But when I was initially writing the 256 color support for the Windows Console about 6 years ago, `TERM=xterm-256color` still emitted colors with just the semicolons as a separator. The colons are more correct, but the semicolons are seemingly more broadly supported.
- drougge 4y agoPart of the problem is probably that termcap uses : as a separator between capabilities. There is \C for colon, but there are implementations that don't support it. If nothing else I know the termcap[info] command in screen doesn't. That doesn't stop terminals from supporting it of course, just from saying they do.