[Fix] Fix sed syntax error in nvm_command_info()

[PeterDaveHello]

No description provided.

[ljharb]

Can you elaborate on this one? it doesn't seem to error out the sed call when I try it locally.

[PeterDaveHello]

The origin one will cause error on GNU sed:
sed: -e expression #1, char 9: Unmatched ) or \)

[ljharb]

Thanks, I've reproduced it - do none of the current travis tests trigger this?

[PeterDaveHello]

I don't think we have test for that yet, won't mind that if you can directly add it.

[PeterDaveHello]

@ljharb is there anything else I can do here? Thanks.

[ljharb]

I'd like to have a regression test before merging this.

[PeterDaveHello]

Any tip please?

[ljharb]

It seems like a unit test for nvm_command_info would trigger that line of code; even if travis-ci didn't trigger the failure, it'd still be good to have the regression test.

[PeterDaveHello]

Is there any regression test example exist in nvm right now so that I can take a look how should it looks like here?

[ljharb]

Just all the existing unit tests - what makes a test a "regression test" is merely that the test was added in response to a bug; to prevent a bug fix from "regressing" in the future.

[PeterDaveHello]

Oh, great, I misunderstood, thanks, just thinking about how the test would look like 🤔

[PeterDaveHello]

@ljharb I'm sorry that I can't make it recently, with all due respect, as it's been a while, and we do locate the bug, know how to fix it, just lack of the test, I wonder if we can

1. Just get this merged, and I'll open another issue to mention this missing test.
   or
2. You'd like to help directly take care of the testing part and get this merged?

It'll be great if we can get this bug fixed and landed in the recent release, thanks a lot.

[PeterDaveHello]

Just simply detect any standard error message in the test, as nvm_command_info should not have a standard error output, what do you think :)

[ljharb]

Seems like this will work!