Скачать или смотреть How to Use sed for String Substitution with Shell Variables in Bash

Learn how to effectively replace strings in files using `sed` and shell variables in Bash. This guide will simplify the process and help you avoid common pitfalls.
---
This video is based on the question https://stackoverflow.com/q/68470187/ asked by the user 'slayedbylucifer' ( https://stackoverflow.com/u/1251660/ ) and on the answer https://stackoverflow.com/a/68470378/ provided by the user 'markp-fuso' ( https://stackoverflow.com/u/7366100/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Sed string substitution with Shell Variable

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Mastering String Substitution with sed and Shell Variables in Bash

When working with shell scripting in Bash, one common task you might encounter is modifying text within files. This can include updating configuration files where values change based on variables in your environment. In this guide, we'll explore how to use sed, a stream editor for filtering and transforming text, to perform string substitution using shell variables effectively.

The Problem: Updating a File with Dynamic Values

Suppose you have a file named testing.list with content referencing a repository version, as shown below:

[[See Video to Reveal this Text or Code Snippet]]

You also have a shell variable named REPOVER containing the new version number:

[[See Video to Reveal this Text or Code Snippet]]

Your goal is to replace the version number in testing.list from 11 to 12. However, using sed while trying to incorporate a shell variable can lead to confusion, particularly around the use of quotes. Let’s break down the process of achieving your objective.

Understanding the Attempts and Challenges

Initial Attempts with Single Quotes

When you first tried to use sed with single quotes:

[[See Video to Reveal this Text or Code Snippet]]

The command resulted in the following output:

[[See Video to Reveal this Text or Code Snippet]]

As evident, the variable $REPOVER didn't get expanded within single quotes. Single quotes suppress variable expansion, which is why it remained as a literal string.

The Double Quotes Dilemma

You then attempted to use double quotes:

[[See Video to Reveal this Text or Code Snippet]]

This led to an error:

[[See Video to Reveal this Text or Code Snippet]]

Here, while double quotes allow for variable expansion, you needed to be cautious. The use of special characters like # needed proper escape handling, which can easily lead to syntax errors when not formatted correctly.

The Solution: A Simplified Approach

To effectively replace the version number, we can apply a more straightforward solution by using the following sed command:

[[See Video to Reveal this Text or Code Snippet]]

Breakdown of the Solution

Pattern Matching: The pattern /[0-9]+ looks for a slash followed by one or more digits and a space after them.

Substitution: The command replaces whatever matched with /${REPOVER} , incorporating the shell variable.

Output: Now when you run this updated command, the output will correctly reflect the modification:

[[See Video to Reveal this Text or Code Snippet]]

Key Takeaways

Single vs. Double Quotes: Using single quotes prevents variable expansion, while double quotes enable it but require careful handling of special characters.

Regular Expressions: Familiarize yourself with sed’s syntax for pattern matching to construct effective search and replace commands.

Conclusion

Using sed for string substitutions in Bash with shell variables can appear daunting at first, particularly due to quoting rules and regular expressions. However, with practice and a clear understanding of how to structure your commands, you can manipulate text in your files seamlessly. The next time you're faced with a similar issue, remember to simplify your commands while ensuring proper syntax.

With these techniques, you'll be well on your way to mastering text manipulation in your Bash scripting endeavors. Happy scripting!