microsoft / microsoft/vscode-cpptools
bash history showing env sh /tmp/Microsoft-MIEngine-Cmd*
@WardenGnaw is already working on this.
Since Dec 7, 2018.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Issue Type: Bug
My bash history showing entries of the form:
env sh /tmp/Microsoft-MIEngine-Cmd*
I use C/C++ tools 0.20.1 and vscode 1.29.1. The command in question is run internally by ether vscode itself or the C/C++. This triggers on every debug run. Adding a space in front the command when it is sent to the shell will prevent it from being logged by bash. I don't expect to see internal commands in the .bash_history file.
Extension version: 0.20.1
VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:07:43.495Z)
OS version: Linux x64 4.18.0-12-generic
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i3-3227U CPU @ 1.90GHz (4 x 943) |
| GPU Status | 2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: unavailable_software video_encode: unavailable_software webgl: enabled webgl2: enabled |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 5.69GB (0.30GB free) |
| Process Argv | --unity-launch |
| Screen Reader | no |
| VM | 0% |
*Adding a space works only if bash is configured not to record such lines as it is in my setup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.