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

Issue when running fzf via SSH in Git Bash #7195

New Issue
Closed
opened 2026-01-31 00:57:30 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:57:30 +00:00
Owner
Copy Link

Originally created by @glen-84 on GitHub (Mar 29, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.10.781.0

Any other software?

Git for Windows: 2.26.0

Steps to reproduce

  1. Create a profile with the commandline: %PROGRAMFILES%/Git/bin/bash.exe -li.
  2. SSH into a Debian64 machine (I'm using VirtualBox).
  3. Run fzf.

Expected behavior

Proper output/rendering.

Actual behavior

When I run where ssh, there are 2 SSH binaries:

  • C:\Program Files\Git\usr\bin\ssh.exe (OpenSSH_8.2p1, OpenSSL 1.1.1e 17 Mar 2020)
  • C:\Windows\System32\OpenSSH\ssh.exe (OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5)
  1. Using the first (which is the default), fzf is completely broken. See screenshot 1 below.
  2. Using the second, fzf appears to work correctly.

Why do they differ? Is there a bug with Git for Windows' SSH binary?

  • Inside the VM:
    • TERM: cygwin
    • LANG: en_ZA.UTF-8
    • LC_ALL: ``

fzf

Originally created by @glen-84 on GitHub (Mar 29, 2020). # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.10.781.0 Any other software? Git for Windows: 2.26.0 ``` # Steps to reproduce 1. Create a profile with the `commandline`: `%PROGRAMFILES%/Git/bin/bash.exe -li`. 2. SSH into a Debian64 machine (I'm using VirtualBox). 3. Run `fzf`. # Expected behavior Proper output/rendering. # Actual behavior When I run `where ssh`, there are 2 SSH binaries: * `C:\Program Files\Git\usr\bin\ssh.exe` (OpenSSH_8.2p1, OpenSSL 1.1.1e 17 Mar 2020) * `C:\Windows\System32\OpenSSH\ssh.exe` (OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5) 1. Using the first (which is the default), `fzf` is completely broken. See screenshot 1 below. 2. Using the second, `fzf` appears to work correctly. Why do they differ? Is there a bug with Git for Windows' SSH binary? * Inside the VM: * TERM: `cygwin` * LANG: `en_ZA.UTF-8` * LC_ALL: `` ![fzf](https://user-images.githubusercontent.com/261509/77848238-b35d0280-71c3-11ea-8313-2f97e4251f2a.gif)
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 00:57:30 +00:00
claunia commented 2026-01-31 00:57:31 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 29, 2020):

If you set TERM to xterm-256color before running fzf, does it work better? (I imagine it doesn’t.)

Even so- Cygwin, before version 3.1 (which git for Windows hasn’t yet updated to), thinks it’s smarter than the windows console and translates all incoming VT sequences back into Win32 API calls. It doesn’t do a very good job of this.

The problem is, conhost has been able to parse VT for the better part of five years now.

Win32-OpenSSH has no such translation.

Closing as external in the meantime :)

@DHowett-MSFT commented on GitHub (Mar 29, 2020): If you set `TERM` to xterm-256color before running fzf, does it work better? (I imagine it doesn’t.) Even so- Cygwin, before version 3.1 (which git for Windows hasn’t yet updated to), thinks it’s smarter than the windows console and translates all incoming VT sequences back into Win32 API calls. It doesn’t do a very good job of this. The problem is, conhost has been able to parse VT for the better part of five years now. Win32-OpenSSH has no such translation. Closing as external in the meantime :)
claunia commented 2026-01-31 00:57:31 +00:00
Author
Owner
Copy Link

@glen-84 commented on GitHub (Mar 29, 2020):

If you set TERM to xterm-256color before running fzf, does it work better? (I imagine it doesn’t.)

It behaves differently, but it's still broken.

Even so- Cygwin, before version 3.1 (which git for Windows hasn’t yet updated to) ...

Thanks for the explanation. So do you think that this is likely to be fixed when Cygwin is updated?

@glen-84 commented on GitHub (Mar 29, 2020): > If you set `TERM` to xterm-256color before running fzf, does it work better? (I imagine it doesn’t.) It behaves differently, but it's still broken. > Even so- Cygwin, before version 3.1 (which git for Windows hasn’t yet updated to) ... Thanks for the explanation. So do you think that this is likely to be fixed when Cygwin is updated?
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 Needs-Tag-Fix Resolution-External
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#7195
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?