Asked  7 Months ago    Answers:  5   Viewed   37 times

I have a Visual Studio project, which is developed locally. Code files have to be deployed to a remote server. The only problem are the URLs they contain, which are hard-coded.

The project contains URLS such as ?page=one. For the link to be valid on the server, it must be /page/one .

I've decided to replace all URLS in my code files with sed before deployment, but I'm stuck on slashes.

I know this is a not a pretty solution, but it's simple and would save me a lot of time. The total number of strings I have to replace is fewer than 10. Total number of files which have to be checked is ~30.

Example describing my situation is below:

Command I'm using:

sed -f replace.txt < a.txt > b.txt

replace.txt which contains all the strings:




Content of b.txt after I run my sed command:


What I want b.txt to contain:




The easiest way would be to use a different delimiter in your search/replace lines, e.g.:


You can use any character as a delimiter that's not part of either string. Or, you could escape it with a backslash:


Which would replace / with foo. You'd want to use the escaped backslash in cases where you don't know what characters might occur in the replacement strings (if they are shell variables, for example).

Tuesday, June 1, 2021
answered 7 Months ago

OS X sed handles the -i argument differently to the Linux version.

You can generate a command that might "work" for both by adding -e in this way:

#      vv
sed -i -e 's|(.*).o:|$(OBJ_DIR)/1.o $(OBJ_DIR)/1.d $(TEST_OBJ_DIR)/1_utest.o:|' $@

OS X sed -i interprets the next thing after the -i as a file extension for a backup copy of the in-place edit. (The Linux version only does this if there is no space between the -i and the extension.) Obviously a side affect of using this is that you will get a backup file with -e as an extension, which you may not want. Please refer to other answers to this question for more details, and cleaner approaches that can be used instead.

The behaviour you see is because OS X sed consumes the s||| as the extension (!) then interprets the next argument as a command - in this case it begins with t, which sed recognizes as a branch-to-label command expecting the target label as an argument - hence the error you see.

If you create a file test you can reproduce the error:

$ sed -i 's|x|y|' test
sed: 1: "test": undefined label 'est'
Thursday, June 3, 2021
answered 7 Months ago

Try this:

sed "s/aaa=.*/aaa=xxx/g"
Sunday, June 27, 2021
answered 6 Months ago

(Compiling an answer from comments, the know-how is by melpomene and AlexP.)

What is that '' after sed -i?

-i means in-place, that is, edit in the file directly.
-i '' means edit in place a file whose name is the empty string.
Since there probably is no file whose name is the empty string, sed complains that it cannot read it.

Note 1 platform dependency:
The syntax of -i is one difference between GNU sed and sed from mac os.

Note 2 "usual" order of arguments:
The -e switch to indicate the sed code allows having it in between file names.
This is a trap (in which I for example got caught embarassingly), by making you trip over your expectations of what you find where in an sed command line.
It allows
sed -i filename -e "expression" AnotherFileName
which is an unintentionally camouflaged version of
sed -i'NoExtensionGiven' "expression" filename AnotherFileName.

Wednesday, July 28, 2021
answered 5 Months ago

parser:foundCharacters: can be called multiple times for one element's contents. It is your responsibility to append all characters from multiple runs of the method to one string.

So unless you can confirm that parser:foundCharacters: doesn't get called again right after the first run, this is expected behavior.

Thursday, September 2, 2021
James Kovacs
answered 4 Months ago
Only authorized users can answer the question. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :