starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

overwrite mode on FreeBSD when crossing space in command line #9232

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

Originally created by @zsbolyoczki on GitHub (Jun 24, 2020).

Environment

Windows Version: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal version: 1.0.1401.0

Issue description

On FreeBSD based servers (and appliances too) the prompt switches to 'overwrite mode' when navigating through a space from the end of the line to the beginning of the line.

Steps to reproduce

  1. Log in to a FreeBSD server (or FBSD based appliance) with ssh. (It doesn't matter which shell (bash, csh, etc.) is being used.)
  2. Try to type a command that's made of more words (or only one word but with a space after it)
  3. Start to navigate from the end of the line to the beginning of the line (either with 'left arrow' or 'Home' or any other way)
  4. Until the 1st space from the right is passed in the command, the command line is in 'insert mode'
  5. Just when the 1st space is passed from the right, the command line switches to 'overwrite mode'

Example #1:
$ commandX

When one is navigating on this one word, it's OK, command line is in 'insert mode'
Once one is typing a space at the end of the line and starts to navigate back to any other letter, the command line changes to 'overwrite mode'

Example #2:
$ commandX paramY paramZ

When navigating backwards from right to left, command line is in 'insert mode' until letter 'Y' is reached. Once the space is crossed next to letter 'Y' the command line switches to 'overwrite mode'.

Expected behavior

Crossing any space in the command line shouldn't switch the command line to 'overwrite mode'.

Working examples which doesn't have this 'switching' behaviour:

  • putty
  • any native linux terminals.
Originally created by @zsbolyoczki on GitHub (Jun 24, 2020). ### Environment Windows Version: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version: 1.0.1401.0 ### Issue description On FreeBSD based servers (and appliances too) the prompt switches to 'overwrite mode' when navigating through a space from the end of the line to the beginning of the line. ### Steps to reproduce 1. Log in to a FreeBSD server (or FBSD based appliance) with ssh. (It doesn't matter which shell (bash, csh, etc.) is being used.) 2. Try to type a command that's made of more words (or only one word but with a space after it) 3. Start to navigate from the end of the line to the beginning of the line (either with 'left arrow' or 'Home' or any other way) 4. Until the 1st space from the right is passed in the command, the command line is in 'insert mode' 5. Just when the 1st space is passed from the right, the command line switches to 'overwrite mode' Example #1: $ commandX When one is navigating on this one word, it's OK, command line is in 'insert mode' Once one is typing a space at the end of the line and starts to navigate back to any other letter, the command line changes to 'overwrite mode' Example #2: $ commandX paramY paramZ When navigating backwards from right to left, command line is in 'insert mode' until letter 'Y' is reached. Once the space is crossed next to letter 'Y' the command line switches to 'overwrite mode'. ### Expected behavior Crossing any space in the command line shouldn't switch the command line to 'overwrite mode'. Working examples which doesn't have this 'switching' behaviour: - putty - any native linux terminals.
claunia added the Area-OutputIssue-BugResolution-Duplicate labels 2026-01-31 01:49:16 +00:00
claunia commented 2026-01-31 01:49:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 24, 2020):

Couple of questions:

  • Which version of ssh are you using? The inbox ssh.exe, or the ssh from a linux distro installed with WSL?
  • does this repro with a legacy console window (conhost.exe)?
@zadjii-msft commented on GitHub (Jun 24, 2020): Couple of questions: * Which version of `ssh` are you using? The inbox `ssh.exe`, or the `ssh` from a linux distro installed with WSL? * does this repro with a legacy console window (conhost.exe)?
claunia commented 2026-01-31 01:49:17 +00:00
Author
Owner
Copy Link

@zsbolyoczki commented on GitHub (Jun 24, 2020):

  • I'm using ssh from WSL (Ubuntu-18.04 (Default))
  • I couldn't find proper way to get current WSL version but "uname -a" returns "4.4.0-18362-Microsoft" if that helps.
  • The issue is there with ssh.exe from cmd and with ssh client from WSL.
@zsbolyoczki commented on GitHub (Jun 24, 2020): - I'm using ssh from WSL (Ubuntu-18.04 (Default)) - I couldn't find proper way to get current WSL version but "uname -a" returns "4.4.0-18362-Microsoft" if that helps. - The issue is there with ssh.exe from cmd and with ssh client from WSL.
claunia commented 2026-01-31 01:49:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 24, 2020):

I believe this is because we don't support #1947...

@DHowett commented on GitHub (Jun 24, 2020): I believe this is because we don't support #1947...
claunia commented 2026-01-31 01:49:17 +00:00
Author
Owner
Copy Link

@zsbolyoczki commented on GitHub (Jun 24, 2020):

seems to be the same issue to this #125 and xterm-256color is affected.

@zsbolyoczki commented on GitHub (Jun 24, 2020): seems to be the same issue to this #125 and xterm-256color is affected.
claunia commented 2026-01-31 01:49:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 24, 2020):

Thanks for following up. I'm gonna make /dup #1947 the master issue for IRM.

@DHowett commented on GitHub (Jun 24, 2020): Thanks for following up. I'm gonna make /dup #1947 the master issue for IRM.
claunia commented 2026-01-31 01:49:18 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 24, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 24, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Issue-Bug 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#9232
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?