wezfurlong

7 ms·

1.
by wezfurlong 4y ago
I don't recall where I saw it, but my understanding was that : was in the original spec but one of the early implementors (Konsole?) misread it and used ; and that erroneous form is what took off, and here we are today.
2.
by wezfurlong 4y ago
The binary is statically linked and embeds several fonts for a consistent, cross-platform, out of the box experience. The on-disk size != RAM usage, and on-disk size really doesn't matter on modern systems, unless you're on a very
3.
by wezfurlong 4y ago
wezterm supports the kitty image protocol (as well as sixel and iterm2), and runs on all major platforms. (disclaimer: I'm the wezterm guy)
4.
by wezfurlong 5y ago
Thanks for giving it a try! I recently moved house and have limited mental bandwidth while I'm setting up the new place--since I don't want to drop the ball on resolving these, I'd appreciate it if you would file separate Gi
5.
by wezfurlong 5y ago
Thanks for sharing! Just before the section you quoted, it says: > Zutty passes the subset of VTTEST screens that we care about FWIW, wezterm passes the subset of vttest screens that I care about too :-p More seriously though, I can&#x27
6.
by wezfurlong 5y ago
You can hate it all you want, I don't mind! ssh support is present because Windows' pty story, while better than 5 years ago, isn't great. The integrated ssh support allows bypassing that layer when running wezterm on Window
7.
by wezfurlong 5y ago
Would you like to submit a PR to add a suitable version of that file to wezterm? FWIW, in my experience so far with wezterm, most people that have run into issues with old rust versions are not running rustup at all, so I feel like somethin
8.
by wezfurlong 5y ago
Thanks for the feedback. Please keep in mind that this project is a free time project, so when you make a generalization that my priorities are wrong and that I have lots of resources, you're a bit off base. I've run vttest a few
9.
by wezfurlong 5y ago
FWIW, wezterm is very slowly building support for `tmux -CC` as well: https://github.com/wez/wezterm/issues/336
10.
by wezfurlong 5y ago
it uses libssh2; agent authentication is supported, but libssh2 doesn't currently support agent forwarding: https://github.com/libssh2/libssh2/issues/535
11.
by wezfurlong 5y ago
Yeah, this stuff is hard. The approach used in wezterm is to use unicode graphemes for cells, and use the unicode width of the grapheme to decide whether a given cell is double-width. Ligatures are handled at rendering time, partly because
12.
by wezfurlong 5y ago
If you're looking for the precise colors in wezterm's defaults, they're here: https://github.com/wez/wezterm/blob/main/term/src/color.rs#L...
13.
by wezfurlong 5y ago
The terminal theme in that screenshot is the builtin wezterm defaults which are a minor evolution of the "Wez" theme that I uploaded to a random wiki years and years ago, and which found its way into the https://github.
14.
by wezfurlong 13y ago
Frame pointers make things easier for tools to get backtraces without requiring complex dwarf unwinders. The observability is something I value more than not being able to use that register for other things.
15.
by wezfurlong 13y ago
The principal difference between the libphenom event dispatcher and the other event libraries is that libphenom can wakeup and dispatch IO events to any of the IO scheduling threads (no thread affinity). Contrast with the libevent approach
16.
by wezfurlong 13y ago
Thanks; good feedback. It's not currently in production at Facebook, but like just about everything we do, we're quickly iterating. Regarding roadmap, we'll try to keep the issue tracker on Github sync'd up with the bro
17.
by wezfurlong 13y ago
All of these are factors in our choice for printf here. Another fun one: FILE on Solaris can only be used with file descriptors whose value fits in 8 bits due to an astonishing degree of backwards ABI compatibility. Also on Solaris, printf
18.
by wezfurlong 13y ago
At a high level, they make it easier to write server (or client) software that deals with multiple concurrent connections (such as HTTP server software, or just about any network facing service these days). They do this by abstracting some
19.
by wezfurlong 13y ago
This is the test code referenced by that commit: https://github.com/facebook/libphenom/blob/master/tests/tpoo...
20.
by wezfurlong 13y ago
We haven't looked at libdispatch specifically; would welcome your feedback on how we compare. We hope we do well here; we've had some nice results: https://github.com/facebook/libphenom/commit/c2753c
21.
by wezfurlong 13y ago
I'm not hot for reimplementing printf, but I did need an interface that made it easy to print diagnostics for various objects; rendering them to the stack and then passing them to the underlying printf implementation makes for a lot of
22.
by wezfurlong 13y ago
We're a bit faster than libevent in terms of dispatch throughput; some benchmarks in this commit message: https://github.com/facebook/libphenom/commit/41b6106f04fe62c... The `tests/bench/iopipe
23.
by wezfurlong 13y ago
What would be a good start would be portable and reliable snapshots with differencing managed by the kernel. Some filesystems offer this capability but it is not available to us in this particular circumstance.
24.
by wezfurlong 13y ago
Watchman uses inotify under the covers (or kqueue or portfs, depending on the OS) and abstracts the differences away. For the Facebook www build it is no longer practical to hash every file to see if it changed because there are so many tha