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

Is it possible to limit the terminal not to go over a single page? #9637

New Issue
Closed
opened 2026-01-31 01:59:49 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 01:59:49 +00:00
Owner
Copy Link

Originally created by @AnFunctionArray on GitHub (Jul 15, 2020).

I have a code that uses SetConsoleCursorPosition to set a position on the screen and write to it. However sometimes it goes over the window buffer and the terminal scrolls down. Is it possible to restrict this and limit the cursor at the current window.

If it's not I would be grateful if you at least point me in the right direction. I've been tinkering with the source code - limiting cursor positions and scrolls all day (both in my application and lately mostly at the terminal source).

Originally created by @AnFunctionArray on GitHub (Jul 15, 2020). I have a code that uses `SetConsoleCursorPosition` to set a position on the screen and write to it. However sometimes it goes over the window buffer and the terminal scrolls down. Is it possible to restrict this and limit the cursor at the current window. If it's not I would be grateful if you at least point me in the right direction. I've been tinkering with the source code - limiting cursor positions and scrolls all day (both in my application and lately mostly at the terminal source).
claunia commented 2026-01-31 01:59:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 16, 2020):

Well, I'd probably start writing code to clamp all your calls to SetCursorPosition within the bounds of the srWindow returned in the CONSOLE_SCREEN_BUFFER_INFO from GetConsoleScreenBufferInfo.

Another thing you could do, which is common for applications which are "painting the entire viewport" (for things like vim, emacs, top, tmux, etc), is use the "alternate screen buffer". This is a special buffer which is exactly the size of the window. You can make edits to the contents of this buffer, and when you leave the buffer, the changes will not be persisted in the "main" buffer, so you don't just have the contents of vim leftover in your history.

You can see a sample of using the alt buffer in a console app here. You'll need to enable ENABLE_VIRTUAL_TERMINAL_PROCESSING, and emit "\x1b[?1049h" to enter the alt buffer, and "\x1b[?1049l" to leave.

You should note that the alt buffer doesn't work exactly right in the Windows Terminal quite yet (see #381, #3492 and others), but it'll work just fine in the vintage console window (conhost.exe)

@zadjii-msft commented on GitHub (Jul 16, 2020): Well, I'd probably start writing code to clamp all your calls to `SetCursorPosition` within the bounds of the `srWindow` returned in the `CONSOLE_SCREEN_BUFFER_INFO` from `GetConsoleScreenBufferInfo`. Another thing you could do, which is common for applications which are "painting the entire viewport" (for things like `vim`, `emacs`, `top`, `tmux`, etc), is use the "alternate screen buffer". This is a special buffer which is exactly the size of the window. You can make edits to the contents of this buffer, and when you leave the buffer, the changes will not be persisted in the "main" buffer, so you don't just have the contents of `vim` leftover in your history. You can see a sample of using the alt buffer in a console app [here](https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#example-of-select-anniversary-update-features). You'll need to enable `ENABLE_VIRTUAL_TERMINAL_PROCESSING`, and emit `"\x1b[?1049h"` to enter the alt buffer, and `"\x1b[?1049l"` to leave. You should note that the alt buffer doesn't work exactly right in the Windows Terminal quite yet (see #381, #3492 and others), but it'll work just fine in the vintage console window (`conhost.exe`)
claunia commented 2026-01-31 01:59:51 +00:00
Author
Owner
Copy Link

@AnFunctionArray commented on GitHub (Jul 16, 2020):

So it looks like this alternative buffer is exactly what I need - but I also need it in Windows Terminal because I depend on the Unicode support.

I guess for now the only thing I can do is wait.

@AnFunctionArray commented on GitHub (Jul 16, 2020): So it looks like this alternative buffer is exactly what I need - but I also need it in Windows Terminal because I depend on the Unicode support. I guess for now the only thing I can do is wait.
claunia commented 2026-01-31 01:59:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 16, 2020):

You can definitely still use the alt buffer currently in the Windows Terminal, there'll just be slight bugs in our implementation. Heck, you can use vim, emacs, htop, etc currently in the Terminal, and they're all pretty fundamentally relying on it.

Currently in the Windows Terminal, your cursor positioning will still be clamped to the size of the viewport, it's just, we'll leave the output in the main buffer for now.

I'd say go ahead and start prototyping with that now and keep an eye on the issues I've linked previously ☺️

@zadjii-msft commented on GitHub (Jul 16, 2020): You can definitely still use the alt buffer currently in the Windows Terminal, there'll just be _slight_ bugs in our implementation. Heck, you can use `vim`, `emacs`, `htop`, etc currently in the Terminal, and they're all pretty fundamentally relying on it. Currently in the Windows Terminal, your cursor positioning will still be clamped to the size of the viewport, it's just, we'll leave the output in the main buffer for now. I'd say go ahead and start prototyping with that _now_ and keep an eye on the issues I've linked previously ☺️
claunia commented 2026-01-31 01:59:51 +00:00
Author
Owner
Copy Link

@AnFunctionArray commented on GitHub (Jul 17, 2020):

@zadjii-msft The alternative buffer isn't locked to the viewpoint - is this an issue? I was able to restrict the viewpoint by commenting some code but I think it would be better is we can write this on stone. Alternatively we could implement a viewpointLock setting to enable. If you think any of those things can be useful/accepted - I can create some code plus I think I can write some tests too.

@AnFunctionArray commented on GitHub (Jul 17, 2020): @zadjii-msft The alternative buffer isn't locked to the viewpoint - is this an issue? I was able to restrict the viewpoint by commenting some code but I think it would be better is we can write this on stone. Alternatively we could implement a `viewpointLock` setting to enable. If you think any of those things can be useful/accepted - I can create some code plus I think I can write some tests too.
claunia commented 2026-01-31 01:59:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 19, 2020):

Sorry for the incredibly delayed response. You're right that the alt buffer in the Terminal currently isn't locked to the viewport. That's something that'll need #381 to actually be finished to fix. I'd rather not implement another workaround - let's just focus on fixing the real root cause 😄

@zadjii-msft commented on GitHub (Aug 19, 2020): Sorry for the incredibly delayed response. You're right that the alt buffer _in the Terminal_ currently isn't locked to the viewport. That's something that'll need #381 to actually be finished to fix. I'd rather not implement another workaround - let's just focus on fixing the real root cause 😄
claunia commented 2026-01-31 01:59:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 23, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 23, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Area-VT Issue-Question Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#9637
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?