100% agree that dealing with Windows paths is a huge pain because of escaping.

It seems like most commands have regex as an option like --regex/-r except for !~ and =~ which are regex by default. If there are other commands that use regex, we should probably be consistent and use the --regex/-r. So, I +1 this for consistency.

Although, there is some weirdness going on in oh-my.nu. I guess I'll have to research it.
This PR

Before this PR

It seems like most commands have regex as an option like --regex/-r except for !~ and =~ which are regex by default. If there are other commands that use regex, we should probably be consistent and use the --regex/-r. So, I +1 this for consistency.

Although, there is some weirdness going on in oh-my.nu. I guess I'll have to research it. This PR Before this PR

some scripts might have to be changed to use --regex now when not using --string 👍

I had to change statements like this

let home = ($nu.home-path | str replace -a '\\' '/')

to this

let home = ($nu.home-path | str replace -a '\' '/')

or

let home = ($nu.home-path | str replace -ar '\\' '/')

This is going to break a bunch of stuff since things work differently now. 82 occurrences in nu_scripts.

I guess it's not really deprecated since it doesn't work the way it used to?

Yeah, it's a breaking change. Not sure how to avoid that. If we added only the warning for --string, but kept it working as before, there would be no way to get substring matching without the warning spam.

OK, let's try.

this also makes it more consistent with other commands such as find or parse which have --regex as an option, but not --string 👌

@kubouch
as you can see in the two commits of mine above, i've used

sd "str replace (.*) --string" "str FOO replace $1" **/*.nu
sd "str replace" "str replace --regex" **/*.nu
sd "str FOO replace" "str replace" **/*.nu

to fix the two repos where i had str replace.

i think this is worth putting in the release notes 😋
either with sd or sed or something else 😉

@amtoine I'm not a big fan of pointing people to other tools if nushell can do the same thing via a pipeline. Granted, sd is meant for this singular purpose.

@amtoine I'm not a big fan of pointing people to other tools if nushell can do the same thing via a pipeline. Granted, sd is meant for this singular purpose.

regardless of the tool, i think we should give some commands for folks to fix their scripts and config 😋

What I did was replace str replace -a blah blah with str replace -ar blah blah and it worked fine. This allowed me to not have to change any parameters but there are more scenarios that that one. That's just the only one I used.