fish-shell
flatpak
Our great sponsors
fish-shell | flatpak | |
---|---|---|
320 | 431 | |
24,502 | 4,042 | |
1.5% | 1.4% | |
9.9 | 9.0 | |
about 14 hours ago | 10 days ago | |
Rust | C | |
GNU General Public License v3.0 or later | GNU Lesser General Public License v3.0 only |
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.
- Devuan アップグレード: 4 から 5 Daedalus へ
flatpak
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Podman Desktop 1.6 released: Even more Kubernetes and Containers features
No, it looks like you have to do it on an application basis.
- how strong is the steam (runtime) sandbox for games?
- Flatpak 1.14.5 Released
-
Been thinking of switching to linux but I am a noob
Flatpak
- FLaNK Stack Weekly for 20 Nov 2023
-
Flathub – The Linux App Store
> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections.
nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions.
That is what Flatpak does. It is Flatpak itself that makes the network connections.
https://github.com/flatpak/flatpak/blob/main/completion/flat...
Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.
- How to prevent/allow chrome from accessing network devices?
-
Linux Phones (2022)
The only performance impact I know of is with the seccomp filter in CPU-bound tasks: https://github.com/flatpak/flatpak/issues/4187
Skimming through the recent comments, there might be a way to optimize some of it.
What are some alternatives?
powerlevel10k - A Zsh theme
steam-runtime - A runtime environment for Steam applications
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
firejail - Linux namespaces and seccomp-bpf sandbox
nushell - A new type of shell
Autodesk-Fusion-360-for-Linux - This is a project, where I give you a way to use Autodesk Fusion 360 on Linux!
oh-my-fish - The Fish Shell Framework
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
nix-gui - Use NixOS Without Coding
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.
com.valvesoftware.Steam