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

Cannot use arrow keys to move around in ruby REPL #3528

New Issue
Closed
opened 2026-01-30 23:23:12 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 23:23:12 +00:00
Owner
Copy Link

Originally created by @jburns24 on GitHub (Aug 23, 2019).

Environment

Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Windows Terminal Version: 0.3.2171.0

Other Software

ruby 2.6.3p62 (2019-04-16 revision 67580) [x64-mingw32]
gems
pry (0.12.2)
irb (1.0.0)
both ruby REPLs

Steps to reproduce

In windows terminal start the ruby REPL pry or irb

type fooar then press the left arrow key to move the cursor back.

Expected behavior

You should be able to use the arrow keys to move around.

Actual behavior

The cursor is stuck at the end of the line.

I tested this behavior in other REPLs such as node, and python and this was not an issue. I then tested this behavior in other shells cmd and powershell (not in windows terminal) and this behavior was not reproducible.

Originally created by @jburns24 on GitHub (Aug 23, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal Version: 0.3.2171.0 ### Other Software ruby 2.6.3p62 (2019-04-16 revision 67580) [x64-mingw32] gems pry (0.12.2) irb (1.0.0) both ruby REPLs # Steps to reproduce In windows terminal start the ruby REPL `pry` or `irb` type `fooar` then press the left arrow key to move the cursor back. <!-- A description of how to trigger this bug. --> # Expected behavior You should be able to use the arrow keys to move around. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior The cursor is stuck at the end of the line. <!-- What's actually happening? --> I tested this behavior in other REPLs such as node, and python and this was not an issue. I then tested this behavior in other shells cmd and powershell (not in windows terminal) and this behavior was not reproducible.
claunia added the Resolution-Duplicate label 2026-01-30 23:23:12 +00:00
claunia commented 2026-01-30 23:23:13 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 23, 2019):

Hi! Thanks for attempting to open an issue. Unfortunately, your title wasn't changed from the original template which makes it very hard for us to track and triage. You are welcome to fix up the title and try again with a new issue.

@ghost commented on GitHub (Aug 23, 2019): Hi! Thanks for attempting to open an issue. Unfortunately, your title wasn't changed from the original template which makes it very hard for us to track and triage. You are welcome to fix up the title and try again with a new issue.
claunia commented 2026-01-30 23:23:14 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (Aug 23, 2019):

I'll fix the title.

@oising commented on GitHub (Aug 23, 2019): I'll fix the title.
claunia commented 2026-01-30 23:23:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 23, 2019):

Hi! Thanks for attempting to open an issue. Unfortunately, your title wasn't changed from the original template which makes it very hard for us to track and triage. You are welcome to fix up the title and try again with a new issue.

@ghost commented on GitHub (Aug 23, 2019): Hi! Thanks for attempting to open an issue. Unfortunately, your title wasn't changed from the original template which makes it very hard for us to track and triage. You are welcome to fix up the title and try again with a new issue.
claunia commented 2026-01-30 23:23:14 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (Aug 23, 2019):

Wow, that's annoying. @miniksa -- this bot is pretty aggressive. I tried to fix the title for OP, but the second I re-open the issue to fix it, the bot closed it again. Is this the experience we want?

@oising commented on GitHub (Aug 23, 2019): Wow, that's annoying. @miniksa -- this bot is pretty aggressive. I tried to fix the title for OP, but the second I re-open the issue to fix it, the bot closed it again. Is this the experience we want?
claunia commented 2026-01-30 23:23:14 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Aug 27, 2019):

Wow, that's annoying. @miniksa Michael Niksa FTE -- this bot is pretty aggressive. I tried to fix the title for OP, but the second I re-open the issue to fix it, the bot closed it again. Is this the experience we want?

No, it's not. Sorry for the delay. I've been swamped. I'll go try to get it to back off.

@miniksa commented on GitHub (Aug 27, 2019): > Wow, that's annoying. @miniksa Michael Niksa FTE -- this bot is pretty aggressive. I tried to fix the title for OP, but the second I re-open the issue to fix it, the bot closed it again. Is this the experience we want? No, it's not. Sorry for the delay. I've been swamped. I'll go try to get it to back off.
claunia commented 2026-01-30 23:23:14 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Aug 27, 2019):

Wow, that's annoying. @miniksa Michael Niksa FTE -- this bot is pretty aggressive. I tried to fix the title for OP, but the second I re-open the issue to fix it, the bot closed it again. Is this the experience we want?

No, it's not. Sorry for the delay. I've been swamped. I'll go try to get it to back off.

@oising, it backs off now for admins and contributors attempting to correct things. My apologies again for the delay.

@miniksa commented on GitHub (Aug 27, 2019): > > Wow, that's annoying. @miniksa Michael Niksa FTE -- this bot is pretty aggressive. I tried to fix the title for OP, but the second I re-open the issue to fix it, the bot closed it again. Is this the experience we want? > > No, it's not. Sorry for the delay. I've been swamped. I'll go try to get it to back off. @oising, it backs off now for admins and contributors attempting to correct things. My apologies again for the delay.
claunia commented 2026-01-30 23:23:15 +00:00
Author
Owner
Copy Link

@jburns24 commented on GitHub (Aug 27, 2019):

@miniksa I should have edited this one I just made another issue https://github.com/microsoft/terminal/issues/2520 you can close this one

@jburns24 commented on GitHub (Aug 27, 2019): @miniksa I should have edited this one I just made another issue https://github.com/microsoft/terminal/issues/2520 you can close this one
claunia commented 2026-01-30 23:23:15 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Aug 29, 2019):

@jburns24, thanks. And sorry for the bot's aggressiveness.

@miniksa commented on GitHub (Aug 29, 2019): @jburns24, thanks. And sorry for the bot's aggressiveness.
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 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#3528
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?