mjhjmtu

I have this string

extension_dir => /some/path/php/extensions/no-debug-non-zts-20160303 => /some/path/php/extensions/no-debug-non-zts-20160303
sqlite3.extension_dir => no value => no value

which is the output of php -i | grep extension_dir.

How can I parse it in bash to get the first /some/path/php/extensions/no-debug-non-zts-20160303?

So far I have tried:

echo $(php -i | grep extension_dir | sed 's/extension_dir => //g' | sed 's/=> .*//g')

but that gives me /some/path/php/extensions/no-debug-non-zts-20160303 sqlite3.no value. I have no idea why it doesn't replace all matches of => .*

My base idea is to get rid of first extension_dir => and than rid of everything after first => including => Probably sed matches things differently than regex.

php -i | sed -n '/extension_dir/s/^[^/]*//;s/ *=>.*$//;p;'

or, as suggested in comments below,

php -i | sed '/extension_dir/!d;s/[^/]*//;s/ *=>.*//'

The sed above replaces your grep and will, for every line that matches extensions_dir, first remove everything up to the first / and then everything from the first => onwards in the modified string. Any spaces before the => are also removed. Lines not matching extensions_dir are ignored.

This will return the wanted path for the first line of input, and an empty line for the second.

To disregard the second line of input, use /^extension_dir/ instead of /extension_dir/ in the sed above. This will discard the second line since does not start with that string.

It's the combination of your two sed scripts that produces the surprising result for the second line of input.

The line is

sqlite3.extension_dir => no value => no value

and the first sed will modify this to

sqlite3.no value => no value

The second sed will then remove the => no value bit at the end.

Note that

echo $( ... )

is a bit useless as it gobbles up the newlines in the output of the command inside $( ... ). Instead test with just the command without the echo or the $( ... ) command substitution.

It is possibly this use of echo that has had you confused about the nature of the output from php -i and grep (two matching lines rather than one).

I can give you a simple awk solution.

php -i | awk -F ' => ' '/extension_dir/print $2; exit'

That will work if you want to lose the sed.

EDIT: Moved exit to inside the block to avoid a syntax error, added spaces around field separator so they won't be output with the resulting filepath, and describe change in body, so stackexchange allows the edit due to minimum character change limitation.

If path doesn't contain spaces, this expression will be enough:

php -i | grep -Po 'extension_dir => K/[^ ]*'

Input

extension_dir => /some/path/php/extensions/no-debug-non-zts-20160303 => /some/path/php/extensions/no-debug-non-zts-20160303
sqlite3.extension_dir => no value => no value

Output

/some/path/php/extensions/no-debug-non-zts-20160303

echo $(php -i | grep -Poie '/some/path/php/extensions/no-debug-non-zts-20160303')