Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
zsbolyoczki opened this issue Jun 24, 2020 · 6 comments
Closed

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

zsbolyoczki opened this issue Jun 24, 2020 · 6 comments
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@zsbolyoczki
Copy link

zsbolyoczki commented Jun 24, 2020 •
edited
Loading

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.
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 24, 2020
@zadjii-msft
Copy link
Member

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 zadjii-msft added Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jun 24, 2020
@zsbolyoczki
Copy link
Author

  • 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.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jun 24, 2020
@DHowett
Copy link
Member

DHowett commented Jun 24, 2020

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

@zsbolyoczki
Copy link
Author

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

@zsbolyoczki zsbolyoczki mentioned this issue Jun 24, 2020
Closed
@DHowett
Copy link
Member

DHowett commented Jun 24, 2020

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

@ghost
Copy link

ghost commented 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 ghost closed this as completed Jun 24, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements Needs-Attention The core contributors need to come back around and look at this ASAP. labels Jun 24, 2020
@andrewnryan andrewnryan mentioned this issue Mar 5, 2021
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DHowett @zadjii-msft @zsbolyoczki