starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

more command doesn't advance to the next screen of text if I press spacebar #19637

New Issue
Open
opened 2026-01-31 06:49:25 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:49:25 +00:00
Owner
Copy Link

Originally created by @adrastogi on GitHub (Apr 5, 2023).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.18.902.0

Windows build number

10.0.23432.1000

Other Software

I tested this in cmd and PowerShell (version info below):

Name              : Microsoft.PowerShell
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 7.3.3.0

Steps to reproduce

  1. Within cmd.exe or pwsh.exe, and with a file that has at least a 'screenful' of text (e.g., call it foo.txt), try using more foo.txt to view the file's contents, one screenful at a time.
  2. After the first screenful is displayed, try pressing spacebar to advance to the next chunk.

Expected Behavior

The Terminal advances to the next page of text.

Actual Behavior

The Terminal remains at the current screen; I see the cursor flashing as normal. I also can't Ctrl+C out of this.

I don't see this behavior in retail Terminal (version 1.16.10262.0)- more behaves as I would expect there.

Originally created by @adrastogi on GitHub (Apr 5, 2023). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.18.902.0 ### Windows build number 10.0.23432.1000 ### Other Software I tested this in cmd and PowerShell (version info below): ``` Name : Microsoft.PowerShell Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Architecture : X64 ResourceId : Version : 7.3.3.0 ``` ### Steps to reproduce 1. Within cmd.exe or pwsh.exe, and with a file that has at least a 'screenful' of text (e.g., call it `foo.txt`), try using `more foo.txt` to view the file's contents, one screenful at a time. 2. After the first screenful is displayed, try pressing spacebar to advance to the next chunk. ### Expected Behavior The Terminal advances to the next page of text. ### Actual Behavior The Terminal remains at the current screen; I see the cursor flashing as normal. I also can't Ctrl+C out of this. I don't see this behavior in retail Terminal (version 1.16.10262.0)- `more` behaves as I would expect there.
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 In-PR Issue-Bug Needs-Tag-Fix Priority-0 Product-Conhost Severity-Blocking
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#19637
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?