Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Fish is great. I love how it works by default. I always felt like zsh required too much setup.
Have you also tried nushell? It's great for manipulating data from e.g.
.csv
or.json
files. It works with structured data like so:I'm honestly just now finding out about all of these different shells, and prompts! It's amazing, and daunting at the same time!
Right now, I'm just using fish since it does the little that I need from the terminal. I am a Linux noob/casual, so working with scripts or CSV or JSON files aren't all that important to me. I will take a look at nushell though! :)
One thing that bothers me about Nushell (even if it doesn't really matter) is honestly just how bloated the table style is, with three columns in each column margin and six columns of enforced line numbers. Why can't it display tables in the same style as regular UNIX commands?
Another thing that bothered me is that the "blessed" way to parse tables from external commands seems very fragile to me. Iirc the builtin parsing commands work solely off table headers, which are locale dependent for many commands, so a script might appear to work fine but suddenly break if an
LC_*
environment variable sneaks in somewhere. The size filter trick works nicely forls
, but doing the same thing becomes painful again when usingdf
.I also found the script syntax (implicit line continuations, command seperation, etc.) difficult to understand but presumably that's just a matter of familiarity.
I'll have to give it another try in the future but for now Fish is good enough for me.
Not OP but I fell instantly in love with fish shell and its design principles.
I've also tried nushell and its design and ideas are really cool. I'm sure it can be very useful for often handling data in the shell. But as a daily thing it was a bit much for me at the time to transition to. 😅 I'd love to explore more sometime though.
Yes, it takes some getting used to. I still use fish as my default shell and use nu for working with data.