starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Same input with different results in terminal and cmd.exe #8811

New Issue
Open
opened 2026-01-31 01:38:37 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:38:37 +00:00
Owner
Copy Link

Originally created by @jnkb on GitHub (Jun 4, 2020).

Environment

Windows build number: Microsoft Windows Pro [Version 10.0.18363.836] x64
Windows Terminal version (if applicable): 1.0.1401.0

Any other software?
stripe cli

Steps to reproduce

Download Stripe CLI (https://github.com/stripe/stripe-cli/releases/tag/v1.4.1)
after "stripe login" (not sure if needed, i was already logged in) using the command
"stripe listen --forward-to https://localhost:44391/api/StripeWebHooks" works on cmd.exe, but not in terminal

Expected behavior

should work as in cmd.exe

Actual behavior

output "unknown flag: --forward-to https://localhost:44391/api/StripeWebHooks"

Screenshot with outputs:
image

Originally created by @jnkb on GitHub (Jun 4, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 ```none Windows build number: Microsoft Windows Pro [Version 10.0.18363.836] x64 Windows Terminal version (if applicable): 1.0.1401.0 Any other software? stripe cli ``` # Steps to reproduce Download Stripe CLI (https://github.com/stripe/stripe-cli/releases/tag/v1.4.1) after "_stripe login_" (not sure if needed, i was already logged in) using the command "_stripe listen --forward-to https://localhost:44391/api/StripeWebHooks_" works on cmd.exe, but not in terminal <!-- A description of how to trigger this bug. --> # Expected behavior should work as in cmd.exe # Actual behavior <!-- What's actually happening? --> output "unknown flag: --forward-to https://localhost:44391/api/StripeWebHooks" Screenshot with outputs: ![image](https://user-images.githubusercontent.com/26929742/83779879-c7722400-a68c-11ea-8328-505dff643015.png)
claunia commented 2026-01-31 01:38:38 +00:00
Author
Owner
Copy Link

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

Well that just doesn't make any sense at all. I have no idea why that wouldn't work. Do other stripe CLI functions work in the Windows Terminal?

If you have WSL installed, could you try running the following for me?

  1. Open cmd.exe (not in the Windows Terminal)
  2. run wsl in that legacy console window
  3. run cmd.exe from within wsl.
  4. try running your command (stripe listen --forward-to ...) again in this window.

This might help narrow the problem down to Conpty vs the entire Windows Terminal.

@zadjii-msft commented on GitHub (Jun 9, 2020): Well that just doesn't make any sense at all. I have no idea why that wouldn't work. Do other `stripe` CLI functions work in the Windows Terminal? If you have WSL installed, could you try running the following for me? 1. Open `cmd.exe` (not in the Windows Terminal) 2. run `wsl` in that legacy console window 3. run `cmd.exe` from within wsl. 4. try running your command (`stripe listen --forward-to ...`) again in this window. This might help narrow the problem down to Conpty vs the entire Windows Terminal.
claunia commented 2026-01-31 01:38:38 +00:00
Author
Owner
Copy Link

@jnkb commented on GitHub (Jun 10, 2020):

Same Problem in the wls cmd:

image

I just found out that it seems to be an encoding problem.
Typing it in manually, it works. Copy & Paste does not work depending on the source.

Try copy & paste from the txt:

terminal_issue_6353.txt

Below the byte arrays of the different inputs.
The space after forward-to is different: 32 vs. 194,160. Don't know how this happend.

[...]
n    110    110
     32    32
-    45    45
-    45    45
f    102    102
o    111    111
r    114    114
w    119    119
a    97    97
r    114    114
d    100    100
-    45    45
t    116    116
o    111    111
      32    194
h    104    160
t    116    104
t    116    116
p    112    116
s    115    112
:    58    115
/    47    58
/    47    47
l    108    47
o    111    108
c    99    111
a    97    99
l    108    97
h    104    108
o    111    104
s    115    111
t    116    115

created with with

var working = "stripe listen --forward-to https://localhost:44391/api/StripeWebHooks";
var notWorking = "stripe listen --forward-to https://localhost:44391/api/StripeWebHooks";
var bytesW = Encoding.UTF8.GetBytes(working);
var bytesNW = Encoding.UTF8.GetBytes(notWorking);
for (int i = 0; i < working.Length; i++)
{
    Console.WriteLine(working[i] + "\t\t" + bytesW[i] + "\t\t" + bytesNW[i]);
}
@jnkb commented on GitHub (Jun 10, 2020): Same Problem in the wls cmd: ![image](https://user-images.githubusercontent.com/26929742/84257892-59a77b80-ab16-11ea-9c59-ae24b3decd8f.png) **I just found out that it seems to be an encoding problem.** Typing it in manually, it works. Copy & Paste does not work depending on the source. Try copy & paste from the txt: [terminal_issue_6353.txt](https://github.com/microsoft/terminal/files/4757998/terminal_issue_6353.txt) Below the byte arrays of the different inputs. The space after forward-to is different: 32 vs. 194,160. Don't know how this happend. ``` [...] n 110 110 32 32 - 45 45 - 45 45 f 102 102 o 111 111 r 114 114 w 119 119 a 97 97 r 114 114 d 100 100 - 45 45 t 116 116 o 111 111 32 194 h 104 160 t 116 104 t 116 116 p 112 116 s 115 112 : 58 115 / 47 58 / 47 47 l 108 47 o 111 108 c 99 111 a 97 99 l 108 97 h 104 108 o 111 104 s 115 111 t 116 115 ``` created with with ```cs var working = "stripe listen --forward-to https://localhost:44391/api/StripeWebHooks"; var notWorking = "stripe listen --forward-to https://localhost:44391/api/StripeWebHooks"; var bytesW = Encoding.UTF8.GetBytes(working); var bytesNW = Encoding.UTF8.GetBytes(notWorking); for (int i = 0; i < working.Length; i++) { Console.WriteLine(working[i] + "\t\t" + bytesW[i] + "\t\t" + bytesNW[i]); } ```
claunia commented 2026-01-31 01:38:39 +00:00
Author
Owner
Copy Link

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

Oh, excellent work with that!

The 160 is probably a &nbsp, IIRC there's some conhost code that just translates those on paste.

The 194 though, no idea what that's doing in there...

@zadjii-msft commented on GitHub (Jun 10, 2020): Oh, excellent work with that! The [160](https://www.fileformat.info/info/unicode/char/00a0/index.htm) is probably a `&nbsp`, IIRC there's some conhost code that just translates those on paste. The 194 though, no idea what that's doing in there...
claunia commented 2026-01-31 01:38:39 +00:00
Author
Owner
Copy Link

@eryksun commented on GitHub (Jun 10, 2020):

The 160 is probably a &nbsp, IIRC there's some conhost code that just translates those on paste.

The 194 though, no idea what that's doing in there...

194 is 0xC2, and "\xc2\xa0" is the UTF-8 encoding of a non-breaking space, U+00A0.

@eryksun commented on GitHub (Jun 10, 2020): > The [160](https://www.fileformat.info/info/unicode/char/00a0/index.htm) is probably a `&nbsp`, IIRC there's some conhost code that just translates those on paste. > > The 194 though, no idea what that's doing in there... 194 is 0xC2, and `"\xc2\xa0"` is the UTF-8 encoding of a non-breaking space, U+00A0.
claunia commented 2026-01-31 01:38:39 +00:00
Author
Owner
Copy Link

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

bc60e6a57f/src/interactivity/win32/Clipboard.cpp (L347-L369)

Indeed!

@DHowett commented on GitHub (Jun 10, 2020): https://github.com/microsoft/terminal/blob/bc60e6a57fb48ad6aa91ae64d478d324f5dc80f4/src/interactivity/win32/Clipboard.cpp#L347-L369 Indeed!
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-TerminalControl Help Wanted Issue-Bug Priority-2 Product-Terminal
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#8811
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?