starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Stopping countdown from scrolling down content of PS window #20475

New Issue
Closed
opened 2026-01-31 07:14:55 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:14:55 +00:00
Owner
Copy Link

Originally created by @GitHubinatrix on GitHub (Sep 13, 2023).

I have read these two to discussions

https://github.com/microsoft/terminal/pull/6062

https://github.com/microsoft/terminal/issues/15059

but as I am not a programmer, just a small time script tweaker, can anyone summarize / explain to me these two discussion in more layman terms?

I have this OK working test code

Write-Host "Line of text at the very top"
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host "Line of text in the middle"
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host
Write-Host "Last line of text"

Write-Host "Executing in:"
Write-Host



# Countdown:

$topRow = [System.Console]::CursorTop

10..0 | ForEach-Object {
    [System.Console]::SetCursorPosition(0, $topRow)

    if ($_ -eq 10) {
        Write-Host $_ -NoNewline
    } else {
        Write-Host " $_" -NoNewline
    }

    Start-Sleep -Seconds 1
    Write-Host " `b" -NoNewline
}



# Here will be the main script

Write-Host
Write-Host "Script has been executed"



# Wait for specific user input (ESC, ENTER, or SPACE) before closing the window:

Write-Host "To close this window press either:
Enter
Space
Esc"
Write-Host

do {
    $key = $Host.UI.RawUI.ReadKey('NoEcho, IncludeKeyDown').Character
} while ($key -notin @(' ', [char]13, [char]27))

which stops the PowerShell window at countdown - and after it ends it then proceeds with execution of the rest of the script

But the problem with it that I have is that every appearing digit makes the PS window scroll down its content to the very bottom - thus I can only see what is above this active counter for less than second afterl scrolling up. I can constantly scroll manually but it always goes back to the bottom to show a new digit. I could of course replace that with a silent countdown like this


$CountdownSeconds = 10
Write-Host "Executing in:"
Write-Host $CountdownSeconds
Write-Host "seconds"
Start-Sleep -Seconds $CountdownSeconds

but at a cost of not being informed then about how much time has left

So is there a way to eat a cake and have it - i.e. to see a digits of countdown at the bottom of window but also at any time to be able to scroll up not have the view thrown back down every second?

Originally created by @GitHubinatrix on GitHub (Sep 13, 2023). I have read these two to discussions https://github.com/microsoft/terminal/pull/6062 https://github.com/microsoft/terminal/issues/15059 but as I am not a programmer, just a small time script tweaker, can anyone summarize / explain to me these two discussion in more layman terms? I have this OK working test code ``` Write-Host "Line of text at the very top" Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host "Line of text in the middle" Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host Write-Host "Last line of text" Write-Host "Executing in:" Write-Host # Countdown: $topRow = [System.Console]::CursorTop 10..0 | ForEach-Object { [System.Console]::SetCursorPosition(0, $topRow) if ($_ -eq 10) { Write-Host $_ -NoNewline } else { Write-Host " $_" -NoNewline } Start-Sleep -Seconds 1 Write-Host " `b" -NoNewline } # Here will be the main script Write-Host Write-Host "Script has been executed" # Wait for specific user input (ESC, ENTER, or SPACE) before closing the window: Write-Host "To close this window press either: Enter Space Esc" Write-Host do { $key = $Host.UI.RawUI.ReadKey('NoEcho, IncludeKeyDown').Character } while ($key -notin @(' ', [char]13, [char]27)) ``` which stops the PowerShell window at countdown - and after it ends it then proceeds with execution of the rest of the script But the problem with it that I have is that every appearing digit makes the PS window scroll down its content to the very bottom - thus I can only see what is above this active counter for less than second afterl scrolling up. I can constantly scroll manually but it always goes back to the bottom to show a new digit. I could of course replace that with a silent countdown like this ``` $CountdownSeconds = 10 Write-Host "Executing in:" Write-Host $CountdownSeconds Write-Host "seconds" Start-Sleep -Seconds $CountdownSeconds ``` but at a cost of not being informed then about how much time has left So is there a way to eat a cake and have it - i.e. to see a digits of countdown at the bottom of window but also at any time to be able to scroll up not have the view thrown back down every second?
claunia commented 2026-01-31 07:14:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 20, 2023):

Ah, you're using the vintage console window, conhost.exe, aren't you/?

Here's a great solution! Go try the Windows Terminal instead. In the Terminal, we've updated this to only snap to the bottom on output, if you're already at the bottom. If you scroll up, then we won't snap to the bottom on output.

@zadjii-msft commented on GitHub (Sep 20, 2023): Ah, you're using the vintage console window, `conhost.exe`, aren't you/? Here's a great solution! Go try the Windows Terminal instead. In the Terminal, we've updated this to only snap to the bottom on output, if you're already at the bottom. If you scroll up, then we won't snap to the bottom on output.
claunia commented 2026-01-31 07:14:58 +00:00
Author
Owner
Copy Link

@GitHubinatrix commented on GitHub (Sep 21, 2023):

Thank you for informing me

But because there are many prerequisites for running Windows Terminal on Windows 10 and my time and skills are limited [and I just know, based on my past experiences, that I will stumble on some issues with upgrading my system] thus I think I will just wait out for the time when I will build a new machine with Windows 11 installed on it - as Wikipedia says that is by default replaced with Windows Terminal since Windows 11 22H2

@GitHubinatrix commented on GitHub (Sep 21, 2023): Thank you for informing me But because there are many [prerequisites](https://github.com/Microsoft/Terminal#prerequisites) for running Windows Terminal on Windows 10 and my time and skills are limited [and I just know, based on my past experiences, that I will stumble on some issues with upgrading my system] thus I think I will just wait out for the time when I will build a new machine with Windows 11 installed on it - as [Wikipedia](https://en.wikipedia.org/wiki/Windows_Terminal) says that is by default replaced with Windows Terminal since Windows 11 22H2
claunia commented 2026-01-31 07:14:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2023):

Ah - those are the pre-reqs for building the Terminal locally. If you just want to install it, you can grab it from the Store, or straight off our Releases page.

@zadjii-msft commented on GitHub (Sep 21, 2023): Ah - those are the pre-reqs for building the Terminal locally. If you just want to install it, you can grab it from the Store, or straight off our [Releases page](https://github.com/microsoft/terminal/releases).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Issue-Question Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20475
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?