Microsoft/vscode

Adapt the bash of busybox.

Open

#170,868 opened on Jan 4, 2023

View on GitHub
 (8 comments) (0 reactions) (1 assignee)TypeScript (10,221 forks)batch import
buggood first issuehelp wantedlinuxterminal-shell-bash

Repository metrics

Stars
 (74,848 stars)
PR merge metrics
 (Avg merge 11h 43m) (1,000 merged PRs in 30d)

Description

  • VSCode Version: 1.74.2
  • Local OS Version: Windows 11 Build 22621
  • Remote OS Version: Alpine Linux v3.17
  • Remote Extension/Connection Type: WSL
  • Logs:

Steps to Reproduce:

  1. Start a terminal.
  2. image

I use busybox bash as /bin/bash (still busybox ash in essence), which is why there is no .bashrc. I hope vs code server can judge whether it is a real bash before using it, if not, treat the bash as ash.

Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: No

Contributor guide

Research direction
Investigate the shell detection logic in VS Code's remote server (likely in src/vs/server/node/remoteTerminalChannel.ts or similar) and add a check for busybox ash when detecting bash.
Tech stack
typescriptjavascript
Domain
backenddeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80