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

command line text editors in Linux (nano,vim) are not working #15295

New Issue
Closed
opened 2026-01-31 04:34:06 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 04:34:06 +00:00
Owner
Copy Link

Originally created by @oholimoli on GitHub (Sep 21, 2021).

Windows Terminal version (or Windows build number)

1.11.2421.0, Microsoft Windows [Version 10.0.18363.1679]

Other Software

No response

Steps to reproduce

When I connect to a linux server with SSH and I try to edit a file with a command line editor like nano or vim it is not possible to edit the text file. Is it possible to fix this?

Expected Behavior

When I use the git bash in Windows everything is ok:

[root@server~]# echo "test" > test.txt
[root@server~]# cat test.txt
hello
[root@server~]# nano test.txt

image

Actual Behavior

[root@server~]# echo "test" > test.txt
[root@server~]# cat test.txt
hello
[root@server~]# nano test.txt

image

Originally created by @oholimoli on GitHub (Sep 21, 2021). ### Windows Terminal version (or Windows build number) 1.11.2421.0, Microsoft Windows [Version 10.0.18363.1679] ### Other Software _No response_ ### Steps to reproduce When I connect to a linux server with SSH and I try to edit a file with a command line editor like nano or vim it is not possible to edit the text file. Is it possible to fix this? ### Expected Behavior When I use the git bash in Windows everything is ok: ``` [root@server~]# echo "test" > test.txt [root@server~]# cat test.txt hello [root@server~]# nano test.txt ``` ![image](https://user-images.githubusercontent.com/47213738/134128306-38a975f0-ebde-49b3-8ff4-745a73875fcf.png) ### Actual Behavior ``` [root@server~]# echo "test" > test.txt [root@server~]# cat test.txt hello [root@server~]# nano test.txt ``` ![image](https://user-images.githubusercontent.com/47213738/134128695-b7332276-9a83-40c7-908d-b6379f81c3be.png)
claunia commented 2026-01-31 04:34:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2021):

Which version of ssh are you using? What's TERM set to once you log into the remote machine? Does this repro in a vintage console window (i.e. conhost.exe?)

@zadjii-msft commented on GitHub (Sep 21, 2021): Which version of `ssh` are you using? What's `TERM` set to once you log into the remote machine? Does this repro in a vintage console window (i.e. `conhost.exe`?)
claunia commented 2026-01-31 04:34:08 +00:00
Author
Owner
Copy Link

@oholimoli commented on GitHub (Sep 21, 2021):

I get the same problem with cmd.exe and conhost.exe

My ssh version is: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

This seems to be the problem.. when I run ssh -V in the GitBash I get:

$ ssh -V
OpenSSH_8.3p1, OpenSSL 1.1.1g  21 Apr 2020

I will try to update SSH for Windows

@oholimoli commented on GitHub (Sep 21, 2021): I get the same problem with cmd.exe and conhost.exe My ssh version is: `OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5` This seems to be the problem.. when I run `ssh -V` in the GitBash I get: ``` $ ssh -V OpenSSH_8.3p1, OpenSSL 1.1.1g 21 Apr 2020 ``` I will try to update SSH for Windows
claunia commented 2026-01-31 04:34:08 +00:00
Author
Owner
Copy Link

@oholimoli commented on GitHub (Sep 21, 2021):

I just updated ssh to OpenSSH_for_Windows_8.6p1, LibreSSL 3.3.3

Still the same problem :(. Somehow I can use nano only in the GitBash.

@oholimoli commented on GitHub (Sep 21, 2021): I just updated ssh to `OpenSSH_for_Windows_8.6p1, LibreSSL 3.3.3` Still the same problem :(. Somehow I can use nano only in the GitBash.
claunia commented 2026-01-31 04:34:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2021):

What's TERM set to once you log into the remote machine? Does this repro in a vintage console window (i.e. conhost.exe?)

@zadjii-msft commented on GitHub (Sep 21, 2021): > What's `TERM` set to once you log into the remote machine? Does this repro in a vintage console window (i.e. `conhost.exe`?)
claunia commented 2026-01-31 04:34:09 +00:00
Author
Owner
Copy Link

@oholimoli commented on GitHub (Sep 21, 2021):

I found the solution here:
https://superuser.com/questions/1172222/issues-editing-files-with-nano-in-bash-windows-10

After connecting to the server I must run the command export TERM=linux

image

I still don't get it why this problem occurs.. why do I need to set an environment variable on my server in order to use nano when I'm connected via ssh? And why was it working in my Git Bash?

@oholimoli commented on GitHub (Sep 21, 2021): I found the solution here: https://superuser.com/questions/1172222/issues-editing-files-with-nano-in-bash-windows-10 After connecting to the server I must run the command `export TERM=linux` ![image](https://user-images.githubusercontent.com/47213738/134183845-81718839-c40e-4fa9-873c-30ee870d4b50.png) I still don't get it why this problem occurs.. why do I need to set an environment variable on my server in order to use nano when I'm connected via ssh? And why was it working in my Git Bash?
claunia commented 2026-01-31 04:34:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2021):

The Windows Terminal doesn't set TERM itself, but the git bash terminal (mintty) likely does. I'd be curious to know what TERM was set to on that machine when you first remoted into it. The Windows Terminal should be roughly equivalent to TERM=xterm-256color, but yea I'd guess that linux would work too.

@zadjii-msft commented on GitHub (Sep 21, 2021): The Windows Terminal doesn't set `TERM` itself, but the git bash terminal (mintty) likely does. I'd be curious to know what `TERM` was set to on that machine when you first remoted into it. The Windows Terminal should be roughly equivalent to `TERM=xterm-256color`, but yea I'd guess that `linux` would work too.
claunia commented 2026-01-31 04:34:09 +00:00
Author
Owner
Copy Link

@oholimoli commented on GitHub (Sep 21, 2021):

The server runs CentOS. The value of TERM was dumb??. I changed it to linux:
echo "export TERM=linux" >> ~/.bashrc

Now everything seems to work fine.

@oholimoli commented on GitHub (Sep 21, 2021): The server runs CentOS. The value of `TERM `was `dumb`??. I changed it to linux: `echo "export TERM=linux" >> ~/.bashrc` Now everything seems to work fine.
claunia commented 2026-01-31 04:34:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2021):

Well, that sure is dumb 😝 glad you figured this out!

@zadjii-msft commented on GitHub (Sep 21, 2021): Well, that sure is `dumb` 😝 glad you figured this out!
claunia commented 2026-01-31 04:34:10 +00:00
Author
Owner
Copy Link

@oholimoli commented on GitHub (Sep 21, 2021):

true :), very lucky to find this solution ... I'm pretty sure I used nano in the past the same way and everything was ok :/.

@oholimoli commented on GitHub (Sep 21, 2021): true :), very lucky to find this solution ... I'm pretty sure I used nano in the past the same way and everything was ok :/.
claunia commented 2026-01-31 04:34:10 +00:00
Author
Owner
Copy Link

@samvanbrussel commented on GitHub (Nov 18, 2021):

vim and nano used to work in the past on my Ubuntu Server 20.04.3 LTS and Raspberry Pi OS 10 (buster). Since I had to do an install of Raspberry Pi OS 11 (bullseye), I noticed that it didn't work any more.

After a lot of research, I noticed it stopped working everywhere, not just on bullseye, so it should be related to my client (Windows Server 2019, ssh via native PowerShell, PowerShell 7 and Command Prompt). So something has changed in Linux (via updates) or Windows (via updates).

Executing export TERM=linux before using nano or vim works. Otherwise, they also work but you get a blank screen and can't see what you're typing (unless you close you editor and go back to the prompt, then everything you did appears).

@samvanbrussel commented on GitHub (Nov 18, 2021): `vim `and `nano `used to work in the past on my Ubuntu Server 20.04.3 LTS and Raspberry Pi OS 10 (buster). Since I had to do an install of Raspberry Pi OS 11 (bullseye), I noticed that it didn't work any more. After a lot of research, I noticed it stopped working everywhere, not just on bullseye, so it should be related to my client (Windows Server 2019, ssh via native PowerShell, PowerShell 7 and Command Prompt). So something has changed in Linux (via updates) or Windows (via updates). Executing `export TERM=linux` before using `nano `or `vim `works. Otherwise, they also work but you get a blank screen and can't see what you're typing (unless you close you editor and go back to the prompt, then everything you did appears).
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 Issue-Question Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Answered
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#15295
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?