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.

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

Character navigation issue #17315

Closed
WillPittenger opened this issue May 23, 2024 · 2 comments
Closed

Character navigation issue #17315

WillPittenger opened this issue May 23, 2024 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase

Comments

@WillPittenger
Copy link

Windows Terminal version

1.20.11271.0

Windows build number

Win32NT 10.0.22631.0 Microsoft Windows NT 10.0.22631.0

Other Software

PS 7.4.2

Steps to reproduce

Paste in 'R🜨'. Now try to put a period immediately after the closing quotes as though you wanted to call one of the string's members. If you do so by visually placing the caret to the immediate right of the closing quote, you'll actually put the new character in the string.

Expected Behavior

As you move the caret back and forth, you'd think it'd move left or right one character the user sees. The user sees 4 characters in that code, 2 in the string and two quotes.

Actual Behavior

Terminal acts like there are 5 characters. It treats 🜨 as two characters. I'm creating this with FF 126.0 and it handle this situation correctly. In this image, the caret was past the end of the string.

image

@WillPittenger WillPittenger added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 23, 2024
Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@lhecker
Copy link
Member

lhecker commented May 24, 2024

Unfortunately, this is a bug in PowerShell, or more specifically in PSReadLine (which is a module in PowerShell that provides the commandline edit experience). If you try your string in a cmd tab for instance, you should notice that it works correctly. I believe this is the most active issue in their repo about this right now: PowerShell/PSReadLine#2358
I've heard internally that they're currently trying to fix this issue, but there's no timeline yet when that may be done (doing it correctly is non-trivial).

@lhecker lhecker closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2024
@lhecker lhecker added the Resolution-External For issues that are outside this codebase label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase
Projects
None yet
Development

No branches or pull requests

2 participants