Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

forceClearScrollbackBuffer conflicts with focusConsoleOnExecute

Open
#2,313 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
powershell

Research direction

Reproduce the issue by enabling powershell.integratedConsole.forceClearScrollbackBuffer and disabling powershell.integratedConsole.focusConsoleOnExecute, then trace the integrated-console execution and focus handling. Done means clearing the scrollback buffer no longer overrides the focus setting, with the cursor remaining in the code window after execution.

Written by the indexing model from the issue text.

Description

Issue-Bug Up for Grabs

Adding the following setting "powershell.integratedConsole.forceClearScrollbackBuffer":true causes the setting "powershell.integratedConsole.focusConsoleOnExecute": false to be ignored.

This means that the focus shifts to the terminal instead of staying inside the code window

System Details

System Details Output


Issue Description

I am experiencing a problem with keeping the focus on the code window instead of the terminal windows

Expected Behaviour

When i run/execute powershell code i expect the focus to stay in the code windows when this setting is added :
"powershell.integratedConsole.focusConsoleOnExecute": false

Actual Behaviour

The setting "powershell.integratedConsole.focusConsoleOnExecute": false is being ignored when i added "powershell.integratedConsole.forceClearScrollbackBuffer": true,, so everytime i execute code my cursor/marker is focused to the terminal windows.

Attached Logs

Follow the instructions in the troubleshooting docs
about capturing and sending logs.

Dominant language
C#
Stars
767
Forks
266
Avg merge
3d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PowerShellEditorServices

All issues in PowerShell/PowerShellEditorServices

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.