[MacOs][Bug][Terminal] sed: illegal option -- r before executing commands

[FaberVitale]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.71.0 - 784b0177c56c607789f9638da7b6bf3230d47a8c
• OS Version: macOS 10.15.7

  System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 192.07 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.20.0 - ~/.nvm/versions/node/v14.20.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 6.14.17 - ~/.nvm/versions/node/v14.20.0/bin/npm

Steps to Reproduce:

1. Open the integrated terminal, then select the Terminal tab.
2. open a new terminal using bash.
3. The following message appears before executing every command:

sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]

Example

$ echo 'hi'
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
hi

It's likely that this issue is caused by e55863c#diff-3d4a2862d6125445f81871e00c3b6d60fa24ef567bdf20c2a185f151a1f86129R125

[stessaris]

The problem is indeed the sed -r in

vscode/src/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh

Line 125 in 784b017

__vsc_current_command="$(builtin history 1 | sed -r 's/ *[0-9]+ +//')"

I guess that the fix should be to use just sed and Basic Regular Expressions. The command should be:
s/ *[0-9][0-9]* *//
(two spaces before the last *).

[wonderfan]

Same issue at my side.

[mouday]

me too! has this problem

[kskliemo]

ugrasma erkek her seyi gordum ayip len sana bide 6 Eyl 2022 Sal 05:10 tarihinde mouday ***@***.***> şunu yazdı:

…

me too! has this problem — Reply to this email directly, view it on GitHub <#159864 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2YGMKSGGAB3NENJ4XFS5TLV42R2DANCNFSM6AAAAAAQDCA7CQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[VSCodeTriageBot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

[mostafa-yasen]

Any update on this?

I also have the same issue.

[Tyriar]

@mostafa-yasen a fix should come in v1.71.1 within the week

[erikvlarsson]

sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]

Having the exact same issue.

[Ndibale]

Should i write the whole code as you typed? Should i put in users directory or where?
The error that comes to my computer is: "sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]"

[EliasOPrado]

sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]

[Tyriar]

The fix for this is coming in 1.71.2, not sure on the release date currently.

[daiyam]

In the meantime, you can use the setting "terminal.integrated.shellIntegration.enabled": false, to disable those freaking errors

[niloct]

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.

(i.e.:)
__vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

[azhuravlev1001]

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.

(i.e.:) __vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

OK well done thank you

[niloct]

OK well done thank you

You're welcome :)

[digiworkzone]

worked!!!
thanks

[davigermano25]

worked

[aromatic-toast]

This worked for me as well! Thank you so much!!!!!!!! This error was incredibly annoying!

[fu-mix]

worked well!!
Thank you so much!

[psparacino]

Fantastic!

[angizerep]

Thank you so much!! It's worked on my machine.

[niloct]

Glad that it helped you guys :)

[mouday]

thank you, it worked!

[olliequ]

Still getting this problem on MacOS 10.14.6.

Any ETD for patch release?

Incredibly annoying. It's funny because this was a rare time where I decided out the blue to update to the latest version of VSCode.

[firmnardians]

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.
(i.e.:) __vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

OK well done thank you

Thanks.

[or4]

I have v1.71.1 and nothing changed

Version: 1.71.1
Commit: e7f30e38c5a4efafeec8ad52861eb772a9ee4dfb

I have error message on each type comamnd in bash

sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]

[or4]

Found solution, it helped me
https://stackoverflow.com/a/73601736/3977725

[milankrushna]

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.

(i.e.:) __vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

Thank a lot
it Worked!

[marcelsev]

Thank you!!!

[FaberVitale]

I can't reproduce it in 1.71.2 👍

Version: 1.71.2
Commit: 74b1f979648cc44d385a2286793c226e611f59e7

[mighty6ft5max]

Had it for weeks. Fixed in 1.71.2.