nix
wezterm
Our great sponsors
nix | wezterm | |
---|---|---|
12 | 131 | |
2,522 | 13,604 | |
2.4% | - | |
9.3 | 9.8 | |
3 days ago | 1 day ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nix
-
I was wrong about rust
If we drop std Rust ceases to be economical due to the time it would take to reimplement the data structures and IO interfaces it provides, not to mention the event loop crate we use (calloop). At that point we'd be relying on so much FFI via eg. nix that the relative safety would be diminished too. After reimplementing all that it's not clear to me that we'd even save that much size, but I suppose it's possible.
-
The guide to signal handling in Rust
Now that we have covered the fundamentals of signals, let's delve into the world of handling signals in Rust! Unlike C, where signal handling is built into the language modules, Rust provides several libraries that enable developers to handle signals with ease. Libraries such as signal_hook, nix, libc, and tokio handle signals that primarily use C bindings to make it possible to work with signals.
-
[Quick Poll] Are You Using Nix for Your Rust Open-Source Projects?
Obviously you meant the nix crate
-
Is there something like unistd.h on Rust?
Finally, there's the nix crate, which provides a safe Rust API over the libc functions.
- Pinning a dependency of a dependency when Cargo.lock is unavailable?
-
Looking for feedback: cargo-changelog
You can take a look here for example: https://github.com/nix-rust/nix/blob/master/CHANGELOG.md
-
An update on Rust coreutils
Unsafe code can in principle speed up I/O by calling libc for special syscalls, but uutils typically uses safe wrappers from nix instead. Very rarely there's a line of unsafe code needed to sand off the edges.
-
Rust maintainer perfectionism, or, the tragedy of Alacritty
This post fails to speak to me on two fronts:
* The `nix` crate is a cornerstone of the Rust development ecosystem: if you do anything that requires POSIX or various nix-specific APIs beyond those wrapped by the standard library, then `nix` most likely provides a high-level and safe* wrapper for them. Perfectionism is a virtue in this context, one that keeps large parts of the Rust ecosystem from accidentally consuming buggy code. The author unfortunately chose a particularly messy and bug-prone corner of the POSIX APIs to wrap, and ran into a correspondingly intensive review process. I've merged simpler wrappers[1][2] with no fuss.
* Alacritty seems to work just fine. I switched to it about two months ago, after using nothing but (heavily customized) rxvt-unicode for a decade. Maybe it's because I don't use ligatures or images in my terminals (I thought we were talking about non-"toy" functionality!), but I haven't found myself wanting for anything beyond what Alacritty already does. And the scrollback seems to work nicely. To summarize: where's the tragedy?
-
What would you change about bitflags?
One thing I'd like to see is a MSRV policy, as its causing problems for downstreams (https://github.com/nix-rust/nix/issues/1555)
- Choosing between Rust and C++ for a new project
wezterm
-
Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1)
wezterm (Linux, Macos & Windows)
- Terminal Emulators Battle Royale – Unicode Edition
-
what terminal emulator would you recommend?
wezterm is pretty good, I've been using it for a long time without any issues. The feature set is honestly huge and I'm probably using 10% of the capabilities, but I like having a lot of options.
-
wezterm suddenly stopped working.
Had the same on hyprland with wezterm and there is already a bug report open for it: https://github.com/wez/wezterm/issues/4483
- Contour: Modern and Fast Terminal Emulator
- Tabby: A terminal for a more modern age
-
The problem that fonts cannot be bolded in wezterm
I had the same problem, and looking at this issue helped: https://github.com/wez/wezterm/discussions/3388
-
Git Blame work around
- [Wezterm](https://github.com/wez/wezterm)
-
Terminal emulators that break from the traditional rendering approach?
and my own humble entry in this space is wezterm: https://wezfurlong.org/wezterm which has a decent population of users in Japan and a handful of arabic/RTL users for the unfinished bidi support.
-
Switching from Emacs. My experience
either Wezterm OR Window-terminal i Personally use WindowTERM with alacritty * when needed since WindowTerm has some weird ncurses issues ,
What are some alternatives?
rust-fuse - Rust library for filesystems in userspace (FUSE)
alacritty - A cross-platform, OpenGL terminal emulator.
tilix - A tiling terminal emulator for Linux using GTK+ 3
kitty - Cross-platform, fast, feature-rich, GPU based terminal
rust - Empowering everyone to build reliable and efficient software.
zellij - A terminal workspace with batteries included
rust-bindgen - Automatically generates Rust FFI bindings to C (and some C++) libraries.
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
cxx - Safe interop between Rust and C++
iTerm2-Color-Schemes - Over 250 terminal color schemes/themes for iTerm/iTerm2. Includes ports to Terminal, Konsole, PuTTY, Xresources, XRDB, Remmina, Termite, XFCE, Tilda, FreeBSD VT, Terminator, Kitty, MobaXterm, LXTerminal, Microsoft's Windows Terminal, Visual Studio, Alacritty
Etherpad - Etherpad: A modern really-real-time collaborative document editor.
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!