output panels reuse
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 25
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The runner creates an output panel every time its goes, should it reuse only one?
vscode 1.4
win10 x64

settings
// Runner configuration
// Ignore shebang line
"runner.ignoreShebang": false,
// Clear Previous Outputs
"runner.clearPreviousOutput": false,
// Specify file extension as key, specify execuable as value
"runner.extensionMap": {
"es": "C:\\Users\\rickm\\AppData\\Roaming\\nvm\\v6.3.0\\babel-node.cmd",
"js": "node",
"jsx": "node"
},
// Specify replacement of shebang line
"runner.shebangMap": {
// "^#!\\s*/usr/bin/python2": "python",
// "^#!\\s*/usr/bin/env python": "python",
// "^#!\\s*/usr/bin/python3": "python3",
// "^#!\\s*/usr/bin/env python3": "python3"
},
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start at the runner entry point that creates an output panel and reproduce the issue by running a file repeatedly in VS Code 1.4 on Windows. Done means repeated runs reuse a single output panel instead of creating another panel each time, while respecting the existing clearPreviousOutput setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100