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

Issues with getting previous command and backspace #14643

New Issue
Closed
opened 2026-01-31 04:15:42 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:15:42 +00:00
Owner
Copy Link

Originally created by @ibqasim on GitHub (Jul 22, 2021).

Windows Terminal version (or Windows build number)

1.8.1521.0

Other Software

Using bash on WSL on Windows Terminal.

Steps to reproduce

Using bash on WSL on Windows Terminal.

  • Type some command and run it.
  • Then try to go back to a previous command (up arrow), and backspace to clear it.

Note that this does not happen every time. Sometimes the command can be cleared as expected, sometimes it cannot.

See below:
bash

The first line ran fine. Then I tried to select a previous command, and was able to clear it fine, and pressed enter. Then again, same thing. But third time I tried to backspace, and it would not go past the li. However, the text actually get's cleared, as if I press enter it gives no output, and I can type additional commands and they work as expected. But visually, the text is still there.

I should add that I have seen similar behaviour before on the online IDE platform repl.it, where commands do not fully get deleted visually.

Apologies if this is a possible duplicate.

Expected Behavior

You should be able to clear the entire command.

Actual Behavior

Only some of the previous command gets cleared, and new text gets appended to it. However the actual text has been deleted, but it doesn't show.

Originally created by @ibqasim on GitHub (Jul 22, 2021). ### Windows Terminal version (or Windows build number) 1.8.1521.0 ### Other Software Using bash on WSL on Windows Terminal. ### Steps to reproduce Using bash on WSL on Windows Terminal. - Type some command and run it. - Then try to go back to a previous command (up arrow), and backspace to clear it. Note that this does not happen every time. Sometimes the command can be cleared as expected, sometimes it cannot. See below: ![bash](https://user-images.githubusercontent.com/8299797/126688983-c7ea17ea-a887-445f-8c4c-0edff6fb406b.png) The first line ran fine. Then I tried to select a previous command, and was able to clear it fine, and pressed enter. Then again, same thing. But third time I tried to backspace, and it would not go past the li. However, the text actually get's cleared, as if I press enter it gives no output, and I can type additional commands and they work as expected. But visually, the text is still there. I should add that I have seen similar behaviour before on the online IDE platform repl.it, where commands do not fully get deleted visually. Apologies if this is a possible duplicate. ### Expected Behavior You should be able to clear the entire command. ### Actual Behavior Only some of the previous command gets cleared, and new text gets appended to it. However the actual text has been deleted, but it doesn't show.
claunia commented 2026-01-31 04:15:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 23, 2021):

What's your PS1 in bash?

@zadjii-msft commented on GitHub (Jul 23, 2021): What's your `PS1` in `bash`?
claunia commented 2026-01-31 04:15:45 +00:00
Author
Owner
Copy Link

@ibqasim commented on GitHub (Jul 23, 2021):

What's your PS1 in bash?

$(horizontal_line)\n\# \t \w $(virtualenv_prompt)\n$

horizontal_line just draws dashes the width of the window.
virtualenv_prompt adds the name of the current python virtual environment.

My PS1 is set as follows (multiple lines are just so it's easier to edit):

PS1=""
PS1="$PS1$(tput setaf 8)\$(horizontal_line)\n"
PS1="$PS1$(tput setaf 1)\# "
PS1="$PS1$(tput setaf 6)\t "
PS1="$PS1$(tput setaf 3)\w "
PS1="$PS1$(tput setaf 5)\$(virtualenv_prompt)\n"
PS1="$PS1$(tput setaf 2)$(tput bold)\$ "
PS1="$PS1$(tput sgr0)"
export PS1
@ibqasim commented on GitHub (Jul 23, 2021): > What's your `PS1` in `bash`? `$(horizontal_line)\n\# \t \w $(virtualenv_prompt)\n$` horizontal_line just draws dashes the width of the window. virtualenv_prompt adds the name of the current python virtual environment. My PS1 is set as follows (multiple lines are just so it's easier to edit): ``` PS1="" PS1="$PS1$(tput setaf 8)\$(horizontal_line)\n" PS1="$PS1$(tput setaf 1)\# " PS1="$PS1$(tput setaf 6)\t " PS1="$PS1$(tput setaf 3)\w " PS1="$PS1$(tput setaf 5)\$(virtualenv_prompt)\n" PS1="$PS1$(tput setaf 2)$(tput bold)\$ " PS1="$PS1$(tput sgr0)" export PS1 ```
claunia commented 2026-01-31 04:15:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 26, 2021):

Yep, that's what I suspected. When you're using escape sequences to format your bash prompt, you need to wrap them up so that bash knows that they're not visible characters.

From the docs

              \[     begin a sequence of non-printing characters,
                     which could be used to embed a terminal con­
                     trol sequence into the prompt
              \]     end a sequence of non-printing characters

If you slap those on either side of the $(tput ...) commands, that should fix it.

@zadjii-msft commented on GitHub (Jul 26, 2021): Yep, that's what I suspected. When you're using escape sequences to format your `bash` prompt, you need to wrap them up so that `bash` knows that they're not visible characters. From [the docs](https://tldp.org/HOWTO/Bash-Prompt-HOWTO/bash-prompt-escape-sequences.html) ``` \[ begin a sequence of non-printing characters, which could be used to embed a terminal con­ trol sequence into the prompt \] end a sequence of non-printing characters ``` If you slap those on either side of the `$(tput ...)` commands, that should fix it.
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 Issue-Question Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Answered
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#14643
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?