nushell
wezterm
Our great sponsors
nushell | wezterm | |
---|---|---|
212 | 131 | |
29,864 | 13,711 | |
2.5% | - | |
9.9 | 9.8 | |
6 days ago | 3 days 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.
nushell
-
NuShell - Ceci n'est pas une |
These are just three small examples of what this shell written in Rust allows. The features are many and many more, but I'll leave it up to you to discover and enjoy them; I'm currently playing around with it and it's giving me a lot of satisfaction and immediacy, now it has a fixed place among the tools I use when working! The project is Open Source, so if you want to contribute, I invite you, as always, to do so, I leave you the link to the repo here!
- Xonsh: Python-powered, cross-platform, Unix-gazing shell
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
Any thoughts on fish as compared to nushell [0]? It's similar to PowerShell in its philosophy and is also written in Rust.
[0] https://github.com/nushell/nushell
-
jc: Converts the output of popular command-line tools to JSON
> In PowerShell, structured output is the default and it seems to work very well.
PowerShell goes a step beyond JSON, by supporting actual mutable objects. So instead of just passing through structured data, you effectively pass around opaque objects that allow you to go back to earlier pipeline stages, and invoke methods, if I understand correctly: https://learn.microsoft.com/en-us/powershell/module/microsof....
I'm rather fond of wrappers like jc and libxo, and experimental shells like https://www.nushell.sh/. These still focus on passing data, not objects with executable methods. On some level, I find this comfortable: Structured data still feels pretty Unix-like, if that makes sense? If I want actual objects, then it's probably time to fire up Python or Ruby.
Knowing when to switch from a shell script to a full-fledged programming language is important, even if your shell is basically awesome and has good programming features.
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
Maybe if the "popular" shells, but http://www.nushell.sh/ is looking better and better
- "<ESC>[31M"? ANSI Terminal security in 2023 and finding 10 CVEs
-
jq 1.7 Released
Yeah agreed, especially now that PowerShell is available cross-platform.
Nushell[1] also seems like a promising alternative, but I haven’t had a chance to play with it yet.
[1]: https://www.nushell.sh/
-
The Case for Nushell
I also discovered an existing discussion[1] related to this topic which includes a link[2] to a "helper to call nushell nuon/json/yaml commands from bash/fish/zsh" and a comment[3] that the current nushell dev focus is "on getting the experience inside nushell right and [we] probably won't be able to dedicate design time to get the interface of native Nu commands with an outside POSIX shell right and stable.".
[0] https://gitlab.com/RancidBacon/notes_public/-/blob/main/note...
[1] "Expose some commands to external world #6554": https://github.com/nushell/nushell/issues/6554
[2] https://github.com/cruel-intentions/devshell-files/blob/mast...
[3] https://github.com/nushell/nushell/issues/6554#issuecomment-...
I appreciate what projects like Nushell and Murex are trying to address, but having a saner scripting language and passing structured data in pipelines is not worth the drawbacks for me.
For one, Bash scripting is not so bad if you set some sane defaults and use ShellCheck. Sure, it has its quirks, but all languages do. Even so, the same golden rule applies: use a "real" programming language if your problem exceeds a certain level of complexity. This is relative and will depend on your discomfort threshold, but using the right tool for the job is always a good practice. No matter how good the shell language is, I would hesitate to write and maintain a complex project in it.
And for general QoL improvements with interactive use, Zsh is a fine shell, while still being POSIX compatible.
[1]: https://github.com/nushell/nushell/blob/main/crates/nu-comma...
[2]: https://github.com/nushell/nushell/issues/5027
[3]: https://github.com/nushell/nushell/issues/9310
-
Simple PowerShell things allowing you to dig a bit deeper than usual
I found nushell (https://www.nushell.sh) to be an impressive replacement "bash" for Windows
In terms of philosophy, think "Powershell but actually intuitive" : Every data is structured but command names are what you expect them to be. I usually don't even need to look at the documentation.
I liked it so much that I also replaced my shell on Linux with it, so I have the same terminal experience across all OSes
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?
fish-shell - The user-friendly command line shell.
alacritty - A cross-platform, OpenGL terminal emulator.
elvish - Powerful scripting language & Versatile interactive shell
kitty - Cross-platform, fast, feature-rich, GPU based terminal
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
zellij - A terminal workspace with batteries included
PowerShell - PowerShell for every system!
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
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
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.