Hey, anyone know why BASH parameter substitution would work on the same system, same account on the command line, but not in a script?
BLAH=${BLAH##+(0)}
Gives "18" for "018" from a command line.
Gives "018" for "018" in a script.
#!/bin/bash explicitly specified
Also no, I'm not going to do it in another language.
This is trivial automation scripting for a cron job, I just have to make sure the processing toolchain doesn't run on files before certain conditions are met.
Legitimately angry at this. If I copy/paste it from the script to a terminal verbatim, it works.
COMPUTERS.
Okay here, now that I'm at a real computer again, here's an example of what I mean:
Okay nevermind, I'm actually just not smart and didn't notice extglob wasn't set.
@SomeEgrets Locale or character set differences?
Same thing if I use pattern replacement like ${BLAH/#+(0)/}
Yes, I could just use sed or something for this, but now this is bothering me. It should work?
(I really just need it to not treat numbers like goddamn octal for filenames that often have leading zeroes)