z VS fish-shell

- Visidata

- z (https://github.com/rupa/z)

- fzf

- vim

- Fastmail

- WireGuard

- draw.io

- PowerShell (it’s difficult to overstate how much PS has improved Windows system administration)

- Microsoft PowerToys

- WSL (alternating joy and extreme frustration)

- Home Assistant

- Airfoil

For even more power use z

https://github.com/rupa/z

- quickly jump to recent directory: https://github.com/rupa/z - however I find it kinda annoying it seems to forget/ignore(?) directories, anyone know of a better version of this?

- quickly opening my personal wiki: https://github.com/francium/dotfiles/blob/master/bin/.local/...

- re-run a script when a file changes: https://github.com/francium/dotfiles/blob/master/bin/.local/...

For `while-watchdo` you, you run it like `while-watchdo "echo hi"`, then in my editor, I have a custom shortcut that does `touch .watchfile` causing the command, in this case `echo hi` to run. I prefer this to tools that retrigger commands as soon as you save _any_ file. Also works in docker containers, edit a file on host, command runs in a container.

2) Well friend, this is where you can have the best of both of worlds. You can just open the file explorer via the CLI. Typically you'll have the xdg-open command that opens the directory in your default file browser. I have that aliased to xdgo. So you can navigate quickly to where you need to be, and then open it visually with xdgo . . There's also other really convenient navigation tools like z (https://github.com/rupa/z) that I can't imagine going without anymore.

I would like to know how you use the terminal and nvim in your daily workflow. Here is mine: I have a shortcut (with raycast) to open alacritty full screen from anywhere. I open alacritty and start the tmux (create work and personal sessions). Then using z navigate to the desired project. Next, I have a bash script pde that opens nvim, and 2 terminal splits below. Nvim opens with alpha-nvim (startify theme). For file explorer I use lir.nvim. Fuzzy finding using fzf-lua. I have harpoon but don't use it very often, instead, I manage buffers with fzf-lua and vim-bbye. When working on multiple files I usually have 2-4 vsplits. I do git stuff mostly using vim-fugitive (gv.vim, resetting hunks with gitsigns.nvim), occasionally git commands from another tmux window. I use auto-save.nvim. My most used command is :F (lsp.bug.format). For movements I use Ctrl+D/U/O/I/, sometimes relative line jumping. Other often movements [q,]q (quickfix jumps), [d,]d (diagnostics jumps), [c,]c (Gitsigns hunks). Alacritty + Neovim view

For general filesystem navigation in my terminal, I'm using z command. But for finer control, I am using the following commands.

z

Do you know about the program z? https://github.com/rupa/z

https://github.com/rupa/z is an awesome command to teleport to your most used directories. It's really handy to jump from a project to another.

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...

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/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

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.

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