peterlits zo

Sorry, but I do not think it is a bug for me... ``` $ echo 'target' | sed 's/miss/hit/' && echo $? target 0 ``` `sed` returns 0 as well...

More information: https://stackoverflow.com/a/15965681/13031497 **Edit**: Sorry about that I misunderstand. I also agree with a new flag.

But the behavior of the application depends on the `regex` library and it looks like they do not want to deal with stream cases (see https://github.com/rust-lang/regex/issues/425) - and that is...

I comment like this: https://github.com/rust-lang/regex/issues/69#issuecomment-1573680606: > I think using braces to invoke the non-just-number variable will be a better idea. > > - `$1asd` = `${1}asd`; > - `$asd` =...

> > \ > > Hi, no one want to see your fucking ass. There is github,not fucking gay hub. We will be very glad to see your bitch mother's...

@chrislombaard Unbelievable that this PR is still not merged. I will deal with it in this weekend (maybe this weekend :) ).

Wait one more week...

-> Move to new PR: #2452

I think using braces to invoke the non-just-number variable will be a better idea. - `$1asd` = `${1}asd`; - `$asd` = Just an error; - `${as}` = OK.

> @PeterlitsZo The issue here isn't "what should it do instead," but that changing it is a breaking change and I have no plans to do a breaking change release...