IssueRaiser

MacOS: "no job control in this shell" prevents Ctrl+C

Type: <b>Bug</b> Every terminal starts with the following message before the first prompt: ``` bash: cannot set terminal process group (8590): Inappropriate ioctl for device bash: no job control in this shell ``` I thought it was related to issue #181939 but it's still present. It prevents ctrl+C out of long-running processes, and other similar commands. If a process is running when the window is closed, CodeHelper crashes. VS Code version: Code 1.79.0 (Universal) (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:29:00.206Z) OS version: Darwin x64 17.7.0 Modes: <details> <summary>System Info</summary> |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4201)| |GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled| |Load (avg)|3, 3, 3| |Memory (System)|64.00GB (29.86GB free)| |Process Argv|-psn_0_725169| |Screen Reader|no| |VM|0%| </details><details><summary>Extensions (28)</summary> Extension|Author (truncated)|Version ---|---|--- laravel-extra-intellisense|ami|0.6.3 vscode-intelephense-client|bme|1.9.5 vscode-tailwindcss|bra|0.9.11 multi-cursor-case-preserve|Car|1.0.5 post

Posted by bitcrush-robin on Jun 9, 2023, 10:33 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments

github (Other)

MacOS: "no job control in this shell" prevents Ctrl+C

bitcrush-robinJun 9, 2023, 10:33 AM

Type: <b>Bug</b> Every terminal starts with the following message before the first prompt: ``` bash: cannot set terminal process group (8590): Inappropriate ioctl for device bash: no job control in this shell ``` I thought it was related to issue #181939 but it's still present. It prevents ctrl+C out of long-running processes, and other similar commands. If a process is running when the window is closed, CodeHelper crashes. VS Code version: Code 1.79.0 (Universal) (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:29:00.206Z) OS version: Darwin x64 17.7.0 Modes: <details> <summary>System Info</summary> |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4201)| |GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled| |Load (avg)|3, 3, 3| |Memory (System)|64.00GB (29.86GB free)| |Process Argv|-psn_0_725169| |Screen Reader|no| |VM|0%| </details><details><summary>Extensions (28)</summary> Extension|Author (truncated)|Version ---|---|--- laravel-extra-intellisense|ami|0.6.3 vscode-intelephense-client|bme|1.9.5 vscode-tailwindcss|bra|0.9.11 multi-cursor-case-preserve|Car|1.0.5 post

Comments (0)

No comments yet. Start the discussion.

Comment on this issue