Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

77%
+5 −0
Q&A How to use grep to print only specific word from a string

I wouldn't use grep. As the other answers already said, it's not the right tool for this job. Considering your specific case (fields separated by /), basename is the most straighforward way, as st...

posted 2y ago by hkotsubo‭  ·  edited 2y ago by hkotsubo‭

Answer
#3: Post edited by user avatar hkotsubo‭ · 2022-07-21T12:26:05Z (almost 2 years ago)
  • I wouldn't use `grep`. As the other answers already said, it's not the right tool for this job.
  • Considering your specific case (fields separated by `/`), `basename` is the most straighforward way, as stated in [Dirk's answer](https://software.codidact.com/posts/286764/286771#answer-286771). I just want to provide some other alternatives.
  • ---
  • # `cut`
  • The `cut` command can separate the input in fields and allows you to get only the ones you need. If you know for sure that the inputs will always be `branches/features/something`, then you can use `/` as separator and get the third field:
  • ```bash
  • echo $CCSR | cut -d / -f 3
  • ```
  • Or, if you don't know how many fields there will be, there's a little trick to get the last one:
  • ```bash
  • echo $CCSR | rev | cut -d / -f 1 | rev
  • ```
  • `rev` reverses the input, so first I reverse it, get the first field and reverse it again. The result will be the last field.
  • # `awk`
  • The `awk` command works in a similar way: we tell it what the separator is and can get specific fields. The difference is that it has a [better way](https://www.gnu.org/software/gawk/manual/gawk.html#Fields) to get the last one, by using the predefined variable `NF`:
  • ```bash
  • echo $CCSR | awk -F / '{print $NF}'
  • ```
  • ---
  • Although `basename` is the most straighforward solution for your case, please note that`cut` and `awk` are more generic, as they can work with different separators and allows you to get specific ones (not only the last).
  • I wouldn't use `grep`. As the other answers already said, it's not the right tool for this job.
  • Considering your specific case (fields separated by `/`), `basename` is the most straighforward way, as stated in [Dirk's answer](https://software.codidact.com/posts/286764/286771#answer-286771). I just want to provide some other alternatives.
  • ---
  • # `cut`
  • The `cut` command can separate the input in fields and allows you to get only the ones you need. If you know for sure that the inputs will always be `branches/features/something`, then you can use `/` as separator and get the third field:
  • ```bash
  • echo $CCSR | cut -d / -f 3
  • ```
  • Or, if you don't know how many fields there will be, there's a little trick to get the last one:
  • ```bash
  • echo $CCSR | rev | cut -d / -f 1 | rev
  • ```
  • `rev` reverses the input, so first I reverse it, get the first field and reverse it again. The result will be the last field.
  • # `awk`
  • The `awk` command works in a similar way: we tell it what the separator is and can get specific fields. The difference is that it has a [better way](https://www.gnu.org/software/gawk/manual/gawk.html#Fields) to get the last one, by using the predefined variable `NF`:
  • ```bash
  • echo $CCSR | awk -F / '{print $NF}'
  • ```
  • ---
  • Although `basename` is the most straighforward solution for your case, please note that`cut` and `awk` are more generic, as they can work with different separators and allows you to get specific fields (not only the last one).
#2: Post edited by user avatar hkotsubo‭ · 2022-07-21T11:45:05Z (almost 2 years ago)
  • I wouldn't use `grep`. As the other answers already said, it's not the right tool for this job.
  • Considering your specific case (fields separated by `/`), `basename` is the most straighforward way, as stated in [Dirk's answer](https://software.codidact.com/posts/286764/286771#answer-286771). I just want to provide some other alternatives.
  • ---
  • # `cut`
  • The `cut` command can separate the input in fields and allows you to get only the ones you need. If you know for sure that the inputs will always be `branches/features/something`, then you can use `/` as separator and get the third field:
  • ```bash
  • echo $CCSR | cut -d / -f 3
  • ```
  • Or, if you don't know how many fields there will be, there's a little trick to get the last one:
  • ```bash
  • echo $CCSR | rev | cut -d / -f 1 | rev
  • ```
  • `rev` reverses the input, so first I reverse it, get the first field and reverse it again. The result will be the last field.
  • # `awk`
  • The `awk` command works in a similar way: we tell it what the separator is and can get specific fields. The difference is that it has a nice syntax to get the last one:
  • ```bash
  • echo $CCSR | awk -F / '{print $NF}'
  • ```
  • ---
  • Although `basename` is the most straighforward solution for your case, please note that`cut` and `awk` are more generic, as they can work with different separators and allows you to get specific ones (not only the last).
  • I wouldn't use `grep`. As the other answers already said, it's not the right tool for this job.
  • Considering your specific case (fields separated by `/`), `basename` is the most straighforward way, as stated in [Dirk's answer](https://software.codidact.com/posts/286764/286771#answer-286771). I just want to provide some other alternatives.
  • ---
  • # `cut`
  • The `cut` command can separate the input in fields and allows you to get only the ones you need. If you know for sure that the inputs will always be `branches/features/something`, then you can use `/` as separator and get the third field:
  • ```bash
  • echo $CCSR | cut -d / -f 3
  • ```
  • Or, if you don't know how many fields there will be, there's a little trick to get the last one:
  • ```bash
  • echo $CCSR | rev | cut -d / -f 1 | rev
  • ```
  • `rev` reverses the input, so first I reverse it, get the first field and reverse it again. The result will be the last field.
  • # `awk`
  • The `awk` command works in a similar way: we tell it what the separator is and can get specific fields. The difference is that it has a [better way](https://www.gnu.org/software/gawk/manual/gawk.html#Fields) to get the last one, by using the predefined variable `NF`:
  • ```bash
  • echo $CCSR | awk -F / '{print $NF}'
  • ```
  • ---
  • Although `basename` is the most straighforward solution for your case, please note that`cut` and `awk` are more generic, as they can work with different separators and allows you to get specific ones (not only the last).
#1: Initial revision by user avatar hkotsubo‭ · 2022-07-21T11:41:12Z (almost 2 years ago)
I wouldn't use `grep`. As the other answers already said, it's not the right tool for this job.

Considering your specific case (fields separated by `/`), `basename` is the most straighforward way, as stated in [Dirk's answer](https://software.codidact.com/posts/286764/286771#answer-286771). I just want to provide some other alternatives.

---

# `cut`

The `cut` command can separate the input in fields and allows you to get only the ones you need. If you know for sure that the inputs will always be `branches/features/something`, then you can use `/` as separator and get the third field:

```bash
echo $CCSR | cut -d / -f 3
```

Or, if you don't know how many fields there will be, there's a little trick to get the last one:

```bash
echo $CCSR | rev | cut -d / -f 1 | rev
```

`rev` reverses the input, so first I reverse it, get the first field and reverse it again. The result will be the last field.

# `awk`

The `awk` command works in a similar way: we tell it what the separator is and can get specific fields. The difference is that it has a nice syntax to get the last one:

```bash
echo $CCSR | awk -F / '{print $NF}'
```

---

Although `basename` is the most straighforward solution for your case, please note that`cut` and `awk` are more generic, as they can work with different separators and allows you to get specific ones (not only the last).