fish-shell
neovim
Our great sponsors
fish-shell | neovim | |
---|---|---|
320 | 1,384 | |
24,551 | 76,465 | |
1.7% | 2.7% | |
9.9 | 10.0 | |
1 day ago | 2 days ago | |
Rust | Vim Script | |
GNU General Public License v3.0 or later | 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.
fish-shell
-
FAQ on the xz-utils backdoor – via a project dev
Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.
https://github.com/fish-shell/fish-shell/releases/tag/3.7.1
https://github.com/fish-shell/fish-shell/issues/7772#issueco...
https://gitlab.archlinux.org/archlinux/packaging/packages/fi...
- Oh My Zsh
- Proposal for porting fish-shell from C++ to Rust
-
Converting the Kernel to C++
A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123
An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust
It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123
-
Day 5 - More or less...
We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.
-
Fish – Update on the Rust Port
They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.
[1] https://github.com/fish-shell/fish-shell/pull/9512
- Devuan アップグレード: 4 から 5 Daedalus へ
neovim
-
Why Neovim is My Text Editor of Choice
As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.
-
Let's See Your Terminal
This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.
-
Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1)
Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads
- Helix - Front-End Power
- Neovim
-
Effective Neovim Setup. A Beginner’s Guide
There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.
-
Aftermath of switching from VSCode to Neovim
All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.
- Neovim is 10 years old today
- Neovide – a simple, no-nonsense, cross-platform GUI for Neovim
- Neovim v0.9.5 Released
What are some alternatives?
powerlevel10k - A Zsh theme
vim9 - An experimental fork of Vim, exploring ways to make Vim script faster and better.
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
helix - A post-modern modal text editor.
nushell - A new type of shell
neovide - No Nonsense Neovim Client in Rust
oh-my-fish - The Fish Shell Framework
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
AstroVim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins [Moved to: https://github.com/AstroNvim/AstroNvim]
tokyonight.nvim - 🏙 A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.