We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
Get used to always have SheBang#!/bin/bash as the first line of the script.
Bash ususally is installed. If not try ksh, it is very similar.
If you want to write compatible script, use dash from Debian and use SheBang #!/bin/sh. But beware, many external programs are a bit different, for example on OS-X.
Just for fun, you can also skip the for loop altogether with: echo -e 1 "\n"{3..99..2}. I'm trying to figure out if there's a way to avoid having to put the 1 in there separately to avoid having the newline character first.
Looping and Skipping
You are viewing a single comment's thread. Return to all comments →
I used "for x in {1..99..2}".
This to me seems like the most concise, elegant way of implementing the for loop, but it seems like it's only a BASH4.0v+ feature.
As per our environment the version of bash we support is 4.3.11
but what if we are programming unix shell script ?
unix shell is bash
It's not true. For example on OpenBSD shell is ksh, not bash.
Get used to always have SheBang
#!/bin/bashas the first line of the script.Bash ususally is installed. If not try
ksh, it is very similar.If you want to write compatible script, use
dashfrom Debian and use SheBang#!/bin/sh. But beware, many external programs are a bit different, for example on OS-X.Nice to know {1..99..22} instead of using $(seq 1 99) which is an external command. Thanks for sharing @kevineid_eid
seq is always faster
yes this discussion has good information shared here. visit https://printerchatsupport.co.uk/epson-printer-support/ for more such information.
Just for fun, you can also skip the for loop altogether with: echo -e 1 "\n"{3..99..2}. I'm trying to figure out if there's a way to avoid having to put the 1 in there separately to avoid having the newline character first.
I didn't have to put the "1" in there:
Maybe bash has changed since you posted this. The problem is the leading lf before the "1" so:
works...but it's totally not what they're probably desiring for a solution.
Nice Bro!!!!!!!!!
Result is Matter LOL!!!!!!
Or this echo -e "\n"{1..99..2} | grep '\w'
The instructions stated to use "for" loops, stay focused please.
Just use printf instead:
This outright fails, now.
i didn't really undestand the loop why 2 in the loop ?
what it means.