Gamma@programming.devM to

Shell Scripting@programming.devEnglish · 1 year ago

How do you shell expand your variables and why?

4

cross-posted to:
programming@programming.dev

3

How do you shell expand your variables and why?

Gamma@programming.devM to

Shell Scripting@programming.devEnglish · 1 year ago

4

cross-posted to:
programming@programming.dev

x-post from !programming@programming.dev: https://programming.dev/post/2165136

Chat

Reptorian@programming.dev
link
fedilink
English
arrow-up
2·
1 year ago
Depends. I use G’MIC (Interpretative language for image processing largely inspired by bash) in CLI.

ig “C:\Users\User.…”

If I need something with ‘$’ in CLI, I’d be using $_path_rc\something_something. Sometimes with “” in case of spaces.

Other than that, I would be just running my own coded command in most case.

Shell Scripting@programming.dev

shell@programming.dev

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !shell@programming.dev

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!

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

4 users / day
8 users / week
23 users / month
41 users / 6 months
9 local subscribers
1.35K subscribers
38 Posts
128 Comments
Modlog