ChatGPT解决这个技术问题 Extra ChatGPT

Extract substring in Bash

Given a filename in the form someletters_12345_moreleters.ext, I want to extract the 5 digits and put them into a variable.

So to emphasize the point, I have a filename with x number of characters then a five digit sequence surrounded by a single underscore on either side then another set of x number of characters. I want to take the 5 digit number and put that into a variable.

I am very interested in the number of different ways that this can be accomplished.

Most of the answers don't seem to answer your question because the question is ambiguous. "I have a filename with x number of characters then a five digit sequence surrounded by a single underscore on either side then another set of x number of characters". By that definition abc_12345_def_67890_ghi_def is a valid input. What do you want to happen? Let's assume there is only one 5 digit sequence. You still have abc_def_12345_ghi_jkl or 1234567_12345_1234567 or 12345d_12345_12345e as valid input based on your definition of input and most of the answers below will not handle this.
This question has an example input that's too specific. Because of that, it got a lot of specific answers for this particular case (digits only, same _ delimiter, input that contains the target string only once etc.). The best (most generic and fastest) answer has, after 10 years, only 7 upvotes, while other limited answers have hundreds. Makes me lose faith in developers 😞
Clickbait title. The meaning of substring function is well established and means getting a part by numerical positions. All the other things, (indexOf, regex) are about search. A 3-month older question that asks precisely about substring in bash, answered the same, but w/o "substring" in the title. Not misleading, but not properly named. Results: the answer about built-in function in most voted question buried 5 screens down with activity sorting; older and more precise question, marked duplicate. stackoverflow.com/questions/219402/…

T
Toby Speight

You can use Parameter Expansion to do this.

If a is constant, the following parameter expansion performs substring extraction:

b=${a:12:5}

where 12 is the offset (zero-based) and 5 is the length

If the underscores around the digits are the only ones in the input, you can strip off the prefix and suffix (respectively) in two steps:

tmp=${a#*_}   # remove prefix ending in "_"
b=${tmp%_*}   # remove suffix starting with "_"

If there are other underscores, it's probably feasible anyway, albeit more tricky. If anyone knows how to perform both expansions in a single expression, I'd like to know too.

Both solutions presented are pure bash, with no process spawning involved, hence very fast.


@SpencerRathbun bash: ${${a#*_}%_*}: bad substitution on my GNU bash 4.2.45.
@jonnyB, Some time in the past that worked. I am told by my coworkers it stopped, and they changed it to be a sed command or something. Looking at it in the history, I was running it in a sh script, which was probably dash. At this point I can't get it to work anymore.
JB, you should clarify that "12" is the offset (zero-based) and "5" is the length. Also, +1 for @gontard 's link that lays it all out!
While running this inside a script as "sh run.sh", one might get Bad Substitution error. To avoid that, change permissions for run.sh (chmod +x run.sh) and then run the script as "./run.sh"
The offset param can be negative too, BTW. You just have to take care not to glue it to the colon, or bash will interpret it as a :- “Use Default Values” substitution. So ${a: -12:5} yields the 5 characters 12 characters from the end, and ${a: -12:-5} the 7 characters between end-12 and end-5.
V
Victor Yarema

Use cut:

echo 'someletters_12345_moreleters.ext' | cut -d'_' -f 2

More generic:

INPUT='someletters_12345_moreleters.ext'
SUBSTRING=$(echo $INPUT| cut -d'_' -f 2)
echo $SUBSTRING

the more generic answer is exactly what i was looking for, thanks
The -f flag takes 1-based indices, rather than the 0-based indices a programmer would be used to.
INPUT=someletters_12345_moreleters.ext SUBSTRING=$(echo $INPUT| cut -d'_' -f 2) echo $SUBSTRING
You should properly use double quotes around the arguments to echo unless you know for sure that the variables cannot contain irregular whitespace or shell metacharacters. See further stackoverflow.com/questions/10067266/…
The number '2' after '-f' is to tell shell to extract the 2nd set of substring.
b
brown.2179

just try to use cut -c startIndx-stopIndx


Is there something like startIndex-lastIndex - 1?
@Niklas In bash, proly startIndx-$((lastIndx-1))
start=5;stop=9; echo "the rain in spain" | cut -c $start-$(($stop-1))
The problem is that the input is dynamic since I also use the pipe to get it so it's basically. git log --oneline | head -1 | cut -c 9-(end -1)
This can be done with cut if break into two parts as line=git log --oneline | head -1` && echo $line | cut -c 9-$((${#line}-1))` but in this particular case, might be better to use sed as git log --oneline | head -1 | sed -e 's/^[a-z0-9]* //g'
J
Johannes Schaub - litb

Generic solution where the number can be anywhere in the filename, using the first of such sequences:

number=$(echo $filename | egrep -o '[[:digit:]]{5}' | head -n1)

Another solution to extract exactly a part of a variable:

number=${filename:offset:length}

If your filename always have the format stuff_digits_... you can use awk:

number=$(echo $filename | awk -F _ '{ print $2 }')

Yet another solution to remove everything except digits, use

number=$(echo $filename | tr -cd '[[:digit:]]')

What if i want to extract the digit/word from last line of the file.
My requirement was to remove few characters at last fileName="filename_timelog.log" number=${filename:0:-12} echo $number O/P: filename
echo $filename | is itself broken -- it should be echo "$filename" | .... See I just assigned a variable, but echo $variable shows something else!. Or, for a bash-only more-efficient approach (at least, more efficient if your TMPDIR is stored on tmpfs, as is conventional on modern distros), <<<"$filename" egrep ...
n
nicerobot

Here's how i'd do it:

FN=someletters_12345_moreleters.ext
[[ ${FN} =~ _([[:digit:]]{5})_ ]] && NUM=${BASH_REMATCH[1]}

Explanation:

Bash-specific:

[[ ]] indicates a conditional expression

=~ indicates the condition is a regular expression

&& chains the commands if the prior command was successful

Regular Expressions (RE): _([[:digit:]]{5})_

_ are literals to demarcate/anchor matching boundaries for the string being matched

() create a capture group

[[:digit:]] is a character class, i think it speaks for itself

{5} means exactly five of the prior character, class (as in this example), or group must match

In english, you can think of it behaving like this: the FN string is iterated character by character until we see an _ at which point the capture group is opened and we attempt to match five digits. If that matching is successful to this point, the capture group saves the five digits traversed. If the next character is an _, the condition is successful, the capture group is made available in BASH_REMATCH, and the next NUM= statement can execute. If any part of the matching fails, saved details are disposed of and character by character processing continues after the _. e.g. if FN where _1 _12 _123 _1234 _12345_, there would be four false starts before it found a match.


This is a generic way that works even if you need to extract more than one thing, as I did.
This is the most generic answer indeed, and should be accepted one. It works for a regular expression, not just a string of characters at a fixed position, or between the same delimiter (which enables cut). It also doesn't rely on executing an external command.
This is great! I adapted this to use different start/stop dilimeters (replace the _) and variable length numbers (. for {5}) for my situation. Can someone break down this black magic and explain it?
@Paul I added more details to my answer. Hope that helps.
j
jperelli

In case someone wants more rigorous information, you can also search it in man bash like this

$ man bash [press return key]
/substring  [press return key]
[press "n" key]
[press "n" key]
[press "n" key]
[press "n" key]

Result:

${parameter:offset}
       ${parameter:offset:length}
              Substring Expansion.  Expands to  up  to  length  characters  of
              parameter  starting  at  the  character specified by offset.  If
              length is omitted, expands to the substring of parameter  start‐
              ing at the character specified by offset.  length and offset are
              arithmetic expressions (see ARITHMETIC  EVALUATION  below).   If
              offset  evaluates  to a number less than zero, the value is used
              as an offset from the end of the value of parameter.  Arithmetic
              expressions  starting  with  a - must be separated by whitespace
              from the preceding : to be distinguished from  the  Use  Default
              Values  expansion.   If  length  evaluates to a number less than
              zero, and parameter is not @ and not an indexed  or  associative
              array,  it is interpreted as an offset from the end of the value
              of parameter rather than a number of characters, and the  expan‐
              sion is the characters between the two offsets.  If parameter is
              @, the result is length positional parameters beginning at  off‐
              set.   If parameter is an indexed array name subscripted by @ or
              *, the result is the length members of the array beginning  with
              ${parameter[offset]}.   A  negative  offset is taken relative to
              one greater than the maximum index of the specified array.  Sub‐
              string  expansion applied to an associative array produces unde‐
              fined results.  Note that a negative offset  must  be  separated
              from  the  colon  by  at least one space to avoid being confused
              with the :- expansion.  Substring indexing is zero-based  unless
              the  positional  parameters are used, in which case the indexing
              starts at 1 by default.  If offset  is  0,  and  the  positional
              parameters are used, $0 is prefixed to the list.

A very important caveat with negative values as stated above: Arithmetic expressions starting with a - must be separated by whitespace from the preceding : to be distinguished from the Use Default Values expansion. So to get last four characters of a var: ${var: -4}
u
user1338062

I'm surprised this pure bash solution didn't come up:

a="someletters_12345_moreleters.ext"
IFS="_"
set $a
echo $2
# prints 12345

You probably want to reset IFS to what value it was before, or unset IFS afterwards!


it's not pure bash solution, I think it works in pure shell (/bin/sh)
+1 You could write this another way to avoid having to unset IFS and positional parameters: IFS=_ read -r _ digs _ <<< "$a"; echo "$digs"
This is subject to pathname expansion! (so it's broken).
P
PEZ

Building on jor's answer (which doesn't work for me):

substring=$(expr "$filename" : '.*_\([^_]*\)_.*')

Regular Expressions is the real deal when you have something complicated and simply counting underscores won't cut it.
Hi, why not [[:digit:]]* instead of [^_]* ?
@YoavKlein [[:digit:]] is certainly a way better choice here for bookkeeping purposes.
w
weston

Following the requirements

I have a filename with x number of characters then a five digit sequence surrounded by a single underscore on either side then another set of x number of characters. I want to take the 5 digit number and put that into a variable.

I found some grep ways that may be useful:

$ echo "someletters_12345_moreleters.ext" | grep -Eo "[[:digit:]]+" 
12345

or better

$ echo "someletters_12345_moreleters.ext" | grep -Eo "[[:digit:]]{5}" 
12345

And then with -Po syntax:

$ echo "someletters_12345_moreleters.ext" | grep -Po '(?<=_)\d+' 
12345

Or if you want to make it fit exactly 5 characters:

$ echo "someletters_12345_moreleters.ext" | grep -Po '(?<=_)\d{5}' 
12345

Finally, to make it be stored in a variable it is just need to use the var=$(command) syntax.


I believe nowadays there is no need to use egrep, the command itself warns you: Invocation as 'egrep' is deprecated; use 'grep -E' instead. I've edited your answer.
佚名

If we focus in the concept of: "A run of (one or several) digits"

We could use several external tools to extract the numbers. We could quite easily erase all other characters, either sed or tr:

name='someletters_12345_moreleters.ext'

echo $name | sed 's/[^0-9]*//g'    # 12345
echo $name | tr -c -d 0-9          # 12345

But if $name contains several runs of numbers, the above will fail:

If "name=someletters_12345_moreleters_323_end.ext", then:

echo $name | sed 's/[^0-9]*//g'    # 12345323
echo $name | tr -c -d 0-9          # 12345323

We need to use regular expresions (regex). To select only the first run (12345 not 323) in sed and perl:

echo $name | sed 's/[^0-9]*\([0-9]\{1,\}\).*$/\1/'
perl -e 'my $name='$name';my ($num)=$name=~/(\d+)/;print "$num\n";'

But we could as well do it directly in bash(1) :

regex=[^0-9]*([0-9]{1,}).*$; \
[[ $name =~ $regex ]] && echo ${BASH_REMATCH[1]}

This allows us to extract the FIRST run of digits of any length surrounded by any other text/characters.

Note: regex=[^0-9]*([0-9]{5,5}).*$; will match only exactly 5 digit runs. :-)

(1): faster than calling an external tool for each short texts. Not faster than doing all processing inside sed or awk for large files.


Change echo $name to echo "$name", or else name=' * 12345 *' will cause your output to contain digits from filenames.
D
Darron

Without any sub-processes you can:

shopt -s extglob
front=${input%%_+([a-zA-Z]).*}
digits=${front##+([a-zA-Z])_}

A very small variant of this will also work in ksh93.


c
codist

Here's a prefix-suffix solution (similar to the solutions given by JB and Darron) that matches the first block of digits and does not depend on the surrounding underscores:

str='someletters_12345_morele34ters.ext'
s1="${str#"${str%%[[:digit:]]*}"}"   # strip off non-digit prefix from str
s2="${s1%%[^[:digit:]]*}"            # strip off non-digit suffix from s1
echo "$s2"                           # 12345

A
Alex Raj Kaliamoorthy

My answer will have more control on what you want out of your string. Here is the code on how you can extract 12345 out of your string

str="someletters_12345_moreleters.ext"
str=${str#*_}
str=${str%_more*}
echo $str

This will be more efficient if you want to extract something that has any chars like abc or any special characters like _ or -. For example: If your string is like this and you want everything that is after someletters_ and before _moreleters.ext :

str="someletters_123-45-24a&13b-1_moreleters.ext"

With my code you can mention what exactly you want. Explanation:

#* It will remove the preceding string including the matching key. Here the key we mentioned is _ % It will remove the following string including the matching key. Here the key we mentioned is '_more*'

Do some experiments yourself and you would find this interesting.


Change echo $var to echo "$var", or else var=' * 12345 *' will cause your output to contain digits from filenames.
h
hankyo

shell cut - print specific range of characters or given part from a string

#method1) using bash

 str=2020-08-08T07:40:00.000Z
 echo ${str:11:8}

#method2) using cut

 str=2020-08-08T07:40:00.000Z
 cut -c12-19 <<< $str

#method3) when working with awk

 str=2020-08-08T07:40:00.000Z
 awk '{time=gensub(/.{11}(.{8}).*/,"\\1","g",$1); print time}' <<< $str

C
Campa

I love sed's capability to deal with regex groups:

> var="someletters_12345_moreletters.ext"
> digits=$( echo "$var" | sed "s/.*_\([0-9]\+\).*/\1/p" -n )
> echo $digits
12345

A slightly more general option would be not to assume that you have an underscore _ marking the start of your digits sequence, hence for instance stripping off all non-numbers you get before your sequence: s/[^0-9]\+\([0-9]\+\).*/\1/p.

> man sed | grep s/regexp/replacement -A 2
s/regexp/replacement/
    Attempt to match regexp against the pattern space.  If successful, replace that portion matched with replacement.  The replacement may contain the special  character  &  to
    refer to that portion of the pattern space which matched, and the special escapes \1 through \9 to refer to the corresponding matching sub-expressions in the regexp.

More on this, in case you're not too confident with regexps:

s is for _s_ubstitute

[0-9]+ matches 1+ digits

\1 links to the group n.1 of the regex output (group 0 is the whole match, group 1 is the match within parentheses in this case)

p flag is for _p_rinting

All escapes \ are there to make sed's regexp processing work.


Change echo $var to echo "$var", or else var=' * 12345 *' will cause your output to contain digits from filenames.
T
Teemu Leisti

Given test.txt is a file containing "ABCDEFGHIJKLMNOPQRSTUVWXYZ"

cut -b19-20 test.txt > test1.txt # This will extract chars 19 & 20 "ST" 
while read -r; do;
> x=$REPLY
> done < test1.txt
echo $x
ST

This is extremely specific to that particular input. The only general solution to the general question (which the OP should have asked) is to use a regexp.
d
diyism

similar to substr('abcdefg', 2-1, 3) in php:

echo 'abcdefg'|tail -c +2|head -c 3

This is extremely specific to that input. The only general solution to the general question (which the OP should have asked) is to use a regexp.
V
Vladimir Kirov

Ok, here goes pure Parameter Substitution with an empty string. Caveat is that I have defined someletters and moreletters as only characters. If they are alphanumeric, this will not work as it is.

filename=someletters_12345_moreletters.ext
substring=${filename//@(+([a-z])_|_+([a-z]).*)}
echo $substring
12345

awesome but requires at least bash v4
echo "$substring", or if someone has IFS=12345 the output will be completely empty.
佚名

A bash solution:

IFS="_" read -r x digs x <<<'someletters_12345_moreleters.ext'

This will clobber a variable called x. The var x could be changed to the var _.

input='someletters_12345_moreleters.ext'
IFS="_" read -r _ digs _ <<<"$input"

c
codeholic24

May be this could help you to get desired output

Code :

your_number=$(echo "someletters_12345_moreleters.ext" | grep -E -o '[0-9]{5}')
echo $your_number

Output :

12345

j
jor

There's also the bash builtin 'expr' command:

INPUT="someletters_12345_moreleters.ext"  
SUBSTRING=`expr match "$INPUT" '.*_\([[:digit:]]*\)_.*' `  
echo $SUBSTRING

expr is not a builtin.
It's also not necessary in light of the =~ operator supported by [[.
m
mjs

Inklusive end, similar to JS and Java implementations. Remove +1 if you do not desire this.

function substring() {
    local str="$1" start="${2}" end="${3}"
    
    if [[ "$start" == "" ]]; then start="0"; fi
    if [[ "$end"   == "" ]]; then end="${#str}"; fi
    
    local length="((${end}-${start}+1))"
    
    echo "${str:${start}:${length}}"
} 

Example:

    substring 01234 0
    01234
    substring 012345 0
    012345
    substring 012345 0 0
    0
    substring 012345 1 1
    1
    substring 012345 1 2
    12
    substring 012345 0 1
    01
    substring 012345 0 2
    012
    substring 012345 0 3
    0123
    substring 012345 0 4
    01234
    substring 012345 0 5
    012345

More example calls:

    substring 012345 0
    012345
    substring 012345 1
    12345
    substring 012345 2
    2345
    substring 012345 3
    345
    substring 012345 4
    45
    substring 012345 5
    5
    substring 012345 6
    
    substring 012345 3 5
    345
    substring 012345 3 4
    34
    substring 012345 2 4
    234
    substring 012345 1 3
    123

function funcname() { merges the legacy ksh syntax function funcname { and the POSIX sh syntax funcname() { in a manner that's incompatible with both legacy ksh and POSIX sh. See wiki.bash-hackers.org/scripting/obsolete
r
russell

A little late, but I just ran across this problem and found the following:

host:/tmp$ asd=someletters_12345_moreleters.ext 
host:/tmp$ echo `expr $asd : '.*_\(.*\)_'`
12345
host:/tmp$ 

I used it to get millisecond resolution on an embedded system that does not have %N for date:

set `grep "now at" /proc/timer_list`
nano=$3
fraction=`expr $nano : '.*\(...\)......'`
$debug nano is $nano, fraction is $fraction

expr is an artifact of the 1970s; as an external command that needs to be forked off as a subprocess, it's deeply inefficient compared to modern shell builtins.
u
user1303800

Here is a substring.sh file

Usage

`substring.sh $TEXT 2 3` # characters 2-3

`substring.sh $TEXT 2` # characters 2 and after 

substring.sh follows this line

#echo "starting substring"
chars=$1
start=$(($2))
end=$3

i=0
o=""
if [[ -z $end ]]; then
  end=`echo "$chars " | wc -c`
else
  end=$((end))
fi
#echo "length is " $e
a=`echo $chars | sed  's/\(.\)/\1 /g'`
#echo "a is " $a
for c in $a
do
  #echo "substring" $i $e $c
  if [[ i -lt $start ]]; then
    : # DO Nothing
  elif [[ i -gt $end ]]; then
    break;
  else
    o="$o$c"
  fi
  i=$(($i+1))
done
#echo substring returning $o
echo $o

Is there a reason you're using legacy backtick command substitution? It creates some fairly nasty bugs that the modern $() syntax doesn't have (particularly with respect to how backslashes are interpreted inside backticks).
(beyond that, why would someone do this, when bash has built-in ${varname:start:length} functionality, which preexisting answers already show how to use?)
...there are also bugs in here that shellcheck.net will flag. Lots of unquoted expansions (which will change a * in the input to a list of filenames), etc.
V
Verdigrass

An easy way to use sed replace:

result=$(echo "someletters_12345_moreleters.ext" | sed 's/.*_\(.*\)_.*/\1/g')
echo $result