Re^3: getting shell expansion to work

I was trying to use the regular expression syntax from bash to match "one or more" of an item. (...) If the extglob shell option is enabled (...)

Thing is, you have to explicitly enable extended pattern matching, which is not enabled by default when the shell is run in non-interactive mode.

Both of these invocations do work for me:

my $r = `/bin/bash -O extglob -c 'echo mc-lang-+([^-])-+([^-])*.rpm'`;

my $r = `/bin/bash -c 'shopt -s extglob\necho mc-lang-+([^-])-+([^-])*
+.rpm'`;
[download]

(i.e., print $r would output mc-lang-4.6.1-140.x86_64.rpm, assuming a file with that name is in the current directory)

Note that when enabling extglob within the command sequence itself (shopt -s extglob, as opposed to the startup option -O extglob), you have to use \n as the statement separator, because when using a semicolon, the shell would parse the line in one go, and produce a syntax error before the shopt command gets a chance to take effect...

Interestingly, on Linux (where /bin/sh typically is a symlink to /bin/bash), the following does work too, for me:

my $r = `shopt -s extglob\necho mc-lang-+([^-])-+([^-])*.rpm`;
[download]

I say "interestingly", because when invoked through the name sh (as Perl does behind the scenes), bash will behave differently in several respects (i.e. it mimics the original bourne shell), which is why I would have expected it to not do extended pattern matching at all. Apparently, the latter is not the case.

Comment on Re^3: getting shell expansion to work Select or Download Code

Replies are listed 'Best First'.
Re^4: getting shell expansion to work by perl-diddler (Chaplain) on Dec 28, 2007 at 20:58 UTC
Gold star (or ++ points in monk-speak :-)). I wondered about that semicolon and the order of processing things -- my only concern (in some 'general' case, not my particular problem) about using "\n" might be portability to a platform where "\n" wasn't the line delimiter.... I should have just "tried it". I too am minorly surprised that '/bin/sh' allows the the non-posix extensions... Definitely not something to rely on... Another solution that I ran across was to use bash as a 'filter' of sorts: $pat='+([^-])-+([^-]).rpm'; $a=`echo 'echo gcc-$pat'\|bash -O extglob`; #-O=capital 'O' [download] It sorta bums me that 'semicolon' isn't equivalent to '\n' in this case. There might be a bug there, somehow: if "shopt cmdhist"=on, then bash tries to store multiline commands in one history entry. Then, if "shopt lithist" is off (I think that's default), then bash will store multi-line commands separated by a semicolon (instead of the newline which would have separated the commands of the multi-line command). As you point out, this isn't equivalent to separation by a newline. It would be a rare error case, but if one concocted a multi-line command that turned on 'extglob'bing, followed by its usage, then that multi-line command sequence would be stored with semi-colons, so on recall, it would contain the non-working semi's instead of the requisite newlines... (and people wonder how it is that I so often break things...:-) ) L	[reply] [d/l]

Replies are listed 'Best First'.

Re^4: getting shell expansion to work
by perl-diddler (Chaplain) on Dec 28, 2007 at 20:58 UTC

I too am minorly surprised that '/bin/sh' allows the the non-posix extensions... Definitely not something to rely on...

Another solution that I ran across was to use bash as a 'filter' of sorts:

$pat='+([^-])-+([^-]).rpm';
$a=`echo 'echo gcc-$pat'|bash -O extglob`;  #-O=capital 'O'
[download]

It would be a rare error case, but if one concocted a multi-line command that turned on 'extglob'bing, followed by its usage, then that multi-line command sequence would be stored with semi-colons, so on recall, it would contain the non-working semi's instead of the requisite newlines... (and people wonder how it is that I so often break things...:-) )
L

[reply]
[d/l]