Shell Scripting

1378 readers

2 users here now

From Ash, Bash and Csh to Xonsh, Ysh and Zsh; all shell languages are welcome here!

Rules:

Follow Lemmy rules!
Posts must relate to shell scripting. (See bottom of sidebar for more information.)
Only make helpful replies to questions. This is not the place for low effort joke answers.
No discussion about piracy or hacking.
If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!
These rules will change as the community grows.

Keep posts about shell scripting! Here are some guidelines to help:

Allowed: Release Announcement of a command-line program designed for scripted use (e.g. bash, bats, awk, jq, coreutils/moreutils)
Allowed: Tutorials on using shell languages or supplementary tools designed for scripted use
Allowed: Code review/help requests for shell languages or supplementary tools designed for scripted use
NOT Allowed: Announcement of a CLI or TUI program that is not designed for scripted use (Yes, your fancy Zsh plugin which pretty-prints the date and time using only builtins is very cool, but unless you actually want to discuss the code itself, please check out !commandline instead!)
NOT Allowed: Domain-specific tutorials that do not involve shell scripting as a core component (e.g. docker-compose, ansible, nix). If you really love one of these, I'm sure there's a community out there ready to talk about them!
NOT Allowed: Code review requests for non-shell programming languages and configuration languages (e.g. Python, Yaml)

In general, if your submission text is primarily shell code, then it is welcome here!

founded 2 years ago

MODERATORS

snowe

gamma

chaoticAnimals

Productivity vs muscle memory/knowledge (self.shell)

submitted 2 weeks ago by TheV2 to c/shell

11 comments fedilink hide all child comments

After a long time I'm in a situation where I sometimes work on a temporary system without my individual setup. Now whenever I might add a new custom (nushell) command that abstracts the usage of CLI tools, I think about the loss of muscle memory/knowledge for these tools and how much time I waste looking them up without my individual setup. No, that's not a huge amount of time, but just out of curiosity I'd like to know how I can minimize this problem as much as possible.

Do you have some tips and solutions to handle this dilemma? I try to shadow and wrap existing commands, whenever it's possible, but that's often not the case. Abbreviations in fish are optimal for this problem in some cases, but I don't think going back to fish as my main shell for this single reason would be worth it.

you are viewing a single comment's thread
view the rest of the comments

[–] Kissaki 1 points 2 weeks ago

What's the nature of the temporary system?

I would consider; remote/temporary systems are not necessarily mine, or setup is not worth it given my concerns on it; There's different options to install or configure existing shells, I could take my config with me; if it's a temporary system maybe it's based on a template that could be adjusted, or auto-setup scripts could be adjusted

It would depend on how much I use it, how much I miss my setup, or how irritated I get because of missing stuff, and considerations of whether it's worth it (to me).

I'm someone who adjusts their environment to their needs and wants, moreso than other colleagues I see. Many people seem to simply accept existing environments and (to me) annoyances.

When I remote into servers, it's not typically where I would use much Nushell functionality. Bash and vim is good enough for those things, with just a little bit of configuration. I don't plan on installing it on work servers, but have recently thought I may install it on my own server for convenience.