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

Garbage characters after line in nano #69

New Issue
Open
opened 2026-01-30 21:41:23 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:41:23 +00:00
Owner
Copy Link

Originally created by @mobluse on GitHub (Feb 10, 2018).

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Microsoft Windows [Version 10.0.17093.1000]
    Ubuntu is most updated.

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    I'm editing a file in GNU nano and when i go to the end of line there are garbage characters after it. The left part shows WSL Ubuntu with original Console and the right part wsltty 1.8.4 (based on mintty). wsltty is correct in this case.
    nano-beep
    apt source beep
    cd beep-1.3/
    nano beep.c

  • What's wrong / what should be happening instead:
    There should not be characters after the last ; on the line starting with $vent));. This bug makes it rather difficult to edit files. The colors are also different, but ought to be the same as in e.g. xterm unless one has some special color scheme. The fonts are the same teletext2.ttf but they have different sizes (16pt and 11pt, respectively) even though they look the same size. I think if one uses a font size it should be the same size on screen in different programs.

Originally created by @mobluse on GitHub (Feb 10, 2018). * Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.17093.1000] Ubuntu is most updated. * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) I'm editing a file in GNU nano and when i go to the end of line there are garbage characters after it. The left part shows WSL Ubuntu with original Console and the right part wsltty 1.8.4 (based on mintty). wsltty is correct in this case. ![nano-beep](https://user-images.githubusercontent.com/5777329/36062286-6eab7082-0e69-11e8-80db-c991f50f2daa.png) `apt source beep` `cd beep-1.3/` `nano beep.c` * What's wrong / what should be happening instead: There should not be characters after the last `;` on the line starting with `$vent));`. This bug makes it rather difficult to edit files. The colors are also different, but ought to be the same as in e.g. xterm unless one has some special color scheme. The fonts are the same [teletext2.ttf](https://github.com/peterkvt80/Muttlee/tree/master/public/assets) but they have different sizes (16pt and 11pt, respectively) even though they look the same size. I think if one uses a font size it should be the same size on screen in different programs.
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-Output Area-VT Issue-Bug Needs-Attention Needs-Repro Needs-Tag-Fix Product-Conhost Resolution-No-Repro
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#69
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?