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

Issue with line wrapping #13730

New Issue
Closed
opened 2026-01-31 03:50:33 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:50:33 +00:00
Owner
Copy Link

Originally created by @vlad-tura on GitHub (May 5, 2021).

Windows Terminal version (or Windows build number)

Microsoft Windows NT 10.0.19041.0

Other Software

Debian (inside wsl)

Steps to reproduce

  1. Open up any WSL distro (tested on Debian)
  2. Write a line long enough that is should wrap (doesn't work if you copy-paste the line, you need to type it).
    xxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Expected Behavior

The caret should continue on the next line.

Actual Behavior

The caret goes to the beginning of the current line

Screen Recording 2021-05-05 at 08 04 06 82 PM

Originally created by @vlad-tura on GitHub (May 5, 2021). ### Windows Terminal version (or Windows build number) Microsoft Windows NT 10.0.19041.0 ### Other Software Debian (inside wsl) ### Steps to reproduce 1) Open up any WSL distro (tested on Debian) 2) Write a line long enough that is should wrap (doesn't work if you copy-paste the line, you need to type it). `xxxxxxxxxxxxxxxxxxxx` xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ### Expected Behavior The caret should continue on the next line. ### Actual Behavior The caret goes to the beginning of the current line ![Screen Recording 2021-05-05 at 08 04 06 82 PM](https://user-images.githubusercontent.com/39374094/117181453-ee296500-addd-11eb-8ef1-cf89d9b3a8c1.gif)
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:50:33 +00:00
claunia commented 2026-01-31 03:50:34 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 5, 2021):

This looks like the classic "bash is not aware of the escape sequences you put into your prompt" issue.

From stack overflow: terminal prompt not wrapping correctly-

Non-printable sequences should be enclosed in \[ and \]. Looking at your PS1 it has a unenclosed sequence after \W. But, the second entry is redundant as well as it repeats the previous statement "1;34".

From Arch wiki-

Note: Wrapping the tput output in \[ \] is recommended by the Bash man page. This helps Bash ignore non-printable characters so that it correctly calculates the size of the prompt. The wrap will not work with command substitution, in which case the raw \1 \2 must be used.

Can you share the output of echo $PS1?

@DHowett commented on GitHub (May 5, 2021): This looks like the classic "bash is not aware of the escape sequences you put into your prompt" issue. From [stack overflow: terminal prompt not wrapping correctly](https://unix.stackexchange.com/questions/105958/terminal-prompt-not-wrapping-correctly)- > Non-printable sequences should be enclosed in \\[ and \\]. Looking at your PS1 it has a unenclosed sequence after \W. But, the second entry is redundant as well as it repeats the previous statement "1;34". From [Arch wiki](https://wiki.archlinux.org/title/Bash/Prompt_customization#Bash_escape_sequences)- > Note: Wrapping the tput output in \\[ \\] is recommended by the Bash man page. This helps Bash ignore non-printable characters so that it correctly calculates the size of the prompt. The wrap will not work with command substitution, in which case the raw \\1 \\2 must be used. Can you share the output of `echo $PS1`?
claunia commented 2026-01-31 03:50:35 +00:00
Author
Owner
Copy Link

@vlad-tura commented on GitHub (May 5, 2021):

You're right, it really does look like that
PS1="\e[0;32m[\u@\h \W]\$ \e[m"

@vlad-tura commented on GitHub (May 5, 2021): You're right, it really does look like that `PS1="\e[0;32m[\u@\h \W]\$ \e[m"`
claunia commented 2026-01-31 03:50:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 5, 2021):

If you change it to this ...

export PS1="\[\e[0;32m\][\u@\h \W]\$ \[\e[m\]"

... how does it change your wrapping issue?

@DHowett commented on GitHub (May 5, 2021): If you change it to this ... ``` export PS1="\[\e[0;32m\][\u@\h \W]\$ \[\e[m\]" ``` ... how does it change your wrapping issue?
claunia commented 2026-01-31 03:50:35 +00:00
Author
Owner
Copy Link

@vlad-tura commented on GitHub (May 5, 2021):

Yep, just did this and it works, thanks a lot!
export PS1="\[\e[0;32m[\u@\h \W]\$\] \[\e[m\]"

@vlad-tura commented on GitHub (May 5, 2021): Yep, just did this and it works, thanks a lot! `export PS1="\[\e[0;32m[\u@\h \W]\$\] \[\e[m\]"`
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 Needs-Attention Needs-Tag-Fix Needs-Triage
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#13730
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?