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

Glitch in menuconfig #305

New Issue
Closed
opened 2026-01-30 21:48:27 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:48:27 +00:00
Owner
Copy Link

Originally created by @Ansuel on GitHub (Jun 16, 2018).

Microsoft Windows [Versione 10.0.17692.1000]

ezgif-5-6159a78bf7

Originally created by @Ansuel on GitHub (Jun 16, 2018). Microsoft Windows [Versione 10.0.17692.1000] ![ezgif-5-6159a78bf7](https://user-images.githubusercontent.com/20289090/41499584-a62f2d7e-7182-11e8-8b31-9b6740110a57.gif)
claunia added the Resolution-Duplicate label 2026-01-30 21:48:27 +00:00
claunia commented 2026-01-30 21:48:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 18, 2018):

There are two issues here:

  1. buffer changes to black when scrolling
  2. Horizontal lines don't work/display

1 is a bug that's already fixed internally.

2 is already being tracked by #194

@zadjii-msft commented on GitHub (Jun 18, 2018): There are two issues here: 1. buffer changes to black when scrolling 2. Horizontal lines don't work/display 1 is a bug that's already fixed internally. 2 is already being tracked by #194
claunia commented 2026-01-30 21:48:28 +00:00
Author
Owner
Copy Link

@Ansuel commented on GitHub (Jun 28, 2018):

@zadjii-msft

the bug 1 is still present in this new insider build... tought it was fixed internally...

@Ansuel commented on GitHub (Jun 28, 2018): @zadjii-msft the bug 1 is still present in this new insider build... tought it was fixed internally...
claunia commented 2026-01-30 21:48:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 2, 2018):

Just because something is fixed internally doesn't mean it'll be out to Insider's immediately. There's a 3 week minimum where code changes bubble up our code tree before they hit the master Windows branch, and typically the 3 weeks is usually closer to 5 weeks.

@zadjii-msft commented on GitHub (Jul 2, 2018): Just because something is fixed internally doesn't mean it'll be out to Insider's immediately. There's a 3 week minimum where code changes bubble up our code tree before they hit the master Windows branch, and typically the 3 weeks is usually closer to 5 weeks.
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 Resolution-Duplicate
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#305
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?