Change:
# Use history if it's available to verify the command as BASH_COMMAND comes in with aliases # resolved if [ "$__vsc_history_verify" = "1" ]; then <del> __vsc_current_command="$(builtin history 1 | sed -r 's/ *[0-9]+ +//')" </del> <ins> __vsc_current_command="$(builtin history 1 | sed 's/ *[0-9]* *//')" </ins> else __vsc_current_command=$BASH_COMMAND fi

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: - OS Version: macOS 10.15.7 Steps to Reproduce: the integrated terminal, then select the tab. a new terminal using bash. following message appears before executing every command: It's likely that this issue is caused by
The problem is indeed the in I guess that the fix should be to use just and . The command should be: (two spaces before the last ).
Same issue at my side.
me too! has this problem
ugrasma erkek her seyi gordum ayip len sana bide 6 Eyl 2022 Sal 05:10 tarihinde mouday yazdı:
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 . See also our . Happy Coding!
Any update on this? I also have the same issue.
a fix should come in v1.71.1 within the week
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.
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 ...]"
sed: illegal option -- r usage: sed script [-Ealn] [-i extension] [file ...]
The fix for this is coming in 1.71.2, not sure on the release date currently.
In the meantime, you can use the setting to disable those freaking errors
The solution is to edit the file on line and use the flag instead of (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac is not a valid option, hence the issue. (i.e.:)
OK well done thank you
You're welcome :)
worked!!! thanks
worked
This worked for me as well! Thank you so much!!!!!!!! This error was incredibly annoying!
worked well!! Thank you so much!
Fantastic!
Glad that it helped you guys :)
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.
Thanks.
I have v1.71.1 and nothing changed I have error message on each type comamnd in bash
Found solution, it helped me
Thank a lot it Worked!
Thank you!!!
I can't reproduce it in 1.71.2
Had it for weeks. Fixed in 1.71.2.