Linux Magazine 296: Pen Testing is available now! Learn to think like an attacker and find resources to get started with penetration testing. This month's DVD includes @fedora Workstation 42 Live and @ubuntubudgie 25.04
https://www.linux-magazine.com/Issues/2025/296?utm_source=mlm
#PenTesting #security #Linux #EUOS #Lomiri #Nushell #Ptcpdump #Python #deborphan #KiCad #NiceGUI #FreshRSS
In Nushell, you don’t even need to use `cd` to change directories, just type the path and go! 
#nushell
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.
Anyone has good resource recommendation for more advanced #nushell scripting? Every single time I just end up going back to Python 
Also seems like no LLM currently understands Nu at any reasonable level.
just finished wiring up nushell in orgmode thanks to this fantastic package https://github.com/herbertjones/nushell-ts-mode/tree/68afe1a8275880995b4d9a122fecf4accca15183
Hello world! This is a human-maintained account for Nushell. Thanks Hachyderm for hosting us.
One way to introduce Nushell is using three "pillars" that form the core of the project:
1. Shell
2. Programming Language
3. Structured Data
1/N #nushell
Imagine a future where we are developing on a #System76 computer running #RedoxOS with #COSMICdesktop and either a #alacritty or a #wezterm terminal running #nushell with #zellij as the multiplexer and #helixeditor as the development environment.
Running #rustlang from top to bottom on your computer. Hopefully it's a future not too far away.
My current Linux desktop 11/2024:
Hardware: ThinkPad T480 with Intel i7 from 2018, dual internal batteries, 512 GB SSD, 32GB RAM.
Software:
- Fedora 41 KDE 
- Distrobox with RHEL9 (UBI) 
- Fish Shell 
(gradually shifting to Nushell)
- Vivaldi Webbrowser 
- KMail/KOrganizer
- Konsole Terminal emulator
- Starship Prompt
- Neovim 
- Podman 
- KleverNotes
- Tokodon for Mastodon
- Steam 
, Bottles and ProtonUP-QT
Hi all, another programming language update from me. It's time to move on from #Nushell, say goodbye to #Junelang, and look to the road ahead.
Some more info here: https://www.sophiajt.com/following-new-paths-ahead/
Been using #nushell for a few months now and I'm entirely unconvinced by it's scripting engine.
The design is so restrictive that I usually just revert to #python for anything more than a few lines of code. Block scoping is such a PITA in particular - why can't I populate my mutables in loops? The final scripts end up being so unnecessarily complex and impossible to maintain which defeats the entire purpose of a shell language.
My shell quest continues to https://www.marceltheshell.org/ next :)
