@rl_dane

Thank you for this wonderful tip

So it's

:match Conceal /^.*$/
:set conceallevel=3

:highlight Conceal NONE

When you're finished, just do

:match

Insert Last Argument of Previous Command in #Bash, #Fish, #Zsh

https://ostechnix.com/insert-last-command-argument-bash-fish-zsh/

here's some more stupid #zsh tricks

https://magnus919.com/2025/05/zsh-hidden-gems-advanced-tricks-that-will-transform-your-command-line-experience/

A small shell function to enable and disable the CPU Turbo in Intel CPUs that use intel_pstate on #Linux
https://gist.github.com/brunomiguel/23fdfc167fb2e3444010dafea3566639

I only tested it on #ZSH, and I'm using it on my .zshrc.

I wrote down some notes on moving from #Zsh to #Fish https://batsov.com/articles/2025/05/20/switching-from-zsh-to-fish/ I hope some of you will find them useful!

$ last | lolcat

I Love the colourful output of lolcat

On FreeBSD, which interactive shell do you primarily use for your non-root user?

If "other", perhaps leave a comment about which shell it is.

$ dmesg|less

$ last|less

$ uptime

$ id|lolcat

En passant mon ordinateur secondaire à #NixOS je me suis mis à tester des logiciels alternatifs :
- #zenbrowser au lieu de #librewolf
- #fish au lieu de #zsh
- #starship au lieu de #spaceship
- #fastfetch au lieu de #neofetch

Et ces changements sont également très agréables !

Can we please have one standard way to define shell completions, that is compatible with all shells?

I'm moving from zsh to nushell, and it's relatively new, and you have to configure completions by writing a lot of code, including a lot of files, it's a nightmare.

It's easier for older shells like zsh or fish only because other people already done it, and some packages include per-shell completions.

There is @carapace_sh which attempts to do the right thing, but having completions in the other place than actual app is not very good idea.

https://usage.jdx.dev/ is trying to do the same but differently, and it has a way for an app to provide a schema for completions. This is step in the right direction, but not many tools support this.

Has anyone tried to put this somehow on the shell level? E.q. app includes a file like `myapp.completions` , and shell have a module which reads the file and generates a list of completions based on user input.

The right way to do this, is probably by defining a standard cross-platform/cross-shell schema. And it can be read by the shell, or by the tool like carapace or usage...

I was using #zsh for the last many years, and I have configured EVERYTHING the way I like.

- Auto-completions
- Per-directory history
- #McFly for Ctrl-R quick search
- Aliases

Now I'm moving to #nushell and I want to configure everything in the same way. But, per-directory history is either broken or non-existent: https://github.com/nushell/nushell/discussions/15670

People do not use per-directory history? This is AWESOME, every time you switch directory you have your entire relevant history at your fingertips. I recommend everyone to try it.

zsh has per-directory-history plugin (i was using oh-my-zsh)
#atuin has even better search, you can filter by workspace/directory/session/...

Atuin has solved missing/broken per-directory history partially, but god I want this to be default in all shells.