twiner
fish-shell
twiner | fish-shell | |
---|---|---|
4 | 320 | |
7 | 24,593 | |
- | 0.9% | |
3.6 | 9.9 | |
4 months ago | 6 days ago | |
Shell | 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.
twiner
-
Linux on a local directory
You need to ensure that you have write access to the directory in which you clone a repository. I do have access, I could create directories and files, and I even ran an instance of Syncthing, synced a "folder" with another computer running Syncthing. It's just that git was having trouble. Following is what I see on the console: bash-5.1# git clone https://github.com/myTerminal/twiner.git Cloning into 'twiner'... remote: Enumerating objects: 450, done. error: unable to get random bytes for temporary file: No such file or directory error: unable to get random bytes for temporary file: No such file or directory fatal: Unable to create temporary file '/var/twiner/.git/objects/pack/tmp_pack_XXXXXX': No such file or directory remote: Counting objects: 100% (22/22), done. remote: Compressing objects: 100% (18/18), done. fatal: fetch-pack: invalid index-pack output
-
Would you consider anything apart from Bash for configuration/setup scripts?
Getting to know Linux better from my initial days with beginner-friendly distributions to stepping into the manual installation of Arch (pacstrap), Debian (debootstrap), and Void (xbps) has taught me a lot more of Bash than I would have expected from myself. I now also maintain my personalized setup scripts along with my dotfiles. Furthermore, I also created twiner as a re-usable tool (that tries to be a lot of things at the same time), which "sort of" helped me deepen my understanding of Bash a little bit more.
-
How I automated my workstation setup
Now that we have a running Linux system, we can bring in my custom setup scripts and set up the rest of the system with a little help from twiner.
-
What my workstation setup is to me
I never had a proper introduction to shell scripting before and as far as I remember, my first shell script was indeed the simple packages installation script for my Linux setup. Needless to say, I started improving my setup scripts and soon realized that most of the scripts that I was writing could be re-used. Around the same time, due to my failure of being able to run a regular Linux distribution on my Dell Precision T3600 desktop due to the incompatibility of the super-old hardware with the latest Xserver packages, I literally had to learn setting up a command-line Linux for graphical use. More configuration meant adding more code to my setup scripts, and all this extra code was a perfect candidate for my library of functions for Linux setup and this led me to create twiner.
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 へ
What are some alternatives?
re-write - Rewrite files and directories into a single file and vice-versa
powerlevel10k - A Zsh theme
calamares - Distribution-independent installer framework
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
git-getter - A utility to get all repositories for a given user
nushell - A new type of shell
yay - Yet another Yogurt - An AUR Helper written in Go
oh-my-fish - The Fish Shell Framework
GNU Emacs - Mirror of GNU Emacs
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
project-euler-solutions - My solutions to ProjectEuler problems in different programming languages
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.