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

Support for native CLI editor #20860

New Issue
Closed
opened 2026-01-31 07:26:10 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:26:10 +00:00
Owner
Copy Link

Originally created by @plante-msft on GitHub (Nov 20, 2023).

Description of idea

It would be helpful during everyday tasks to be able to view and edit files in Windows via CLI. Default support for nano for example.

Expected behavior

Using 'nano file.txt' opens up the file in the CLI for editing.
image

Actual behavior

Error displayed.
image

Originally created by @plante-msft on GitHub (Nov 20, 2023). # Description of idea It would be helpful during everyday tasks to be able to view and edit files in Windows via CLI. Default support for `nano` for example. # Expected behavior Using 'nano file.txt' opens up the file in the CLI for editing. ![image](https://github.com/microsoft/terminal/assets/150482134/de1dd5a4-6de8-4e49-80a1-f944726fe10e) # Actual behavior Error displayed. ![image](https://github.com/microsoft/terminal/assets/150482134/fe4a3217-abd1-448c-9832-90b0c58b7ab9)
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 07:26:10 +00:00
claunia commented 2026-01-31 07:26:11 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 21, 2023):

Just an outside observer here, but it looks to me like the issue isn't with terminal; it's that you don't have nano installed on your system. It's on the winget package manager too, so if your Windows install is recent, you should be able to install from there. Left panel is Powershell in Terminal before installing, right panel is after.

Screenshot 2023-11-20 211134
@ghost commented on GitHub (Nov 21, 2023): Just an outside observer here, but it looks to me like the issue isn't with terminal; it's that you don't have `nano` installed on your system. It's on the `winget` package manager too, so if your Windows install is recent, you should be able to install from there. Left panel is Powershell in Terminal before installing, right panel is after. <img width="1500" alt="Screenshot 2023-11-20 211134" src="https://github.com/microsoft/terminal/assets/122397995/79f0b880-05c6-4e75-b612-eac4a2c3b7af">
claunia commented 2026-01-31 07:26:11 +00:00
Author
Owner
Copy Link

@b-cpu commented on GitHub (Dec 3, 2023):

I think he's asking for a native, built-in way to edit text files in Terminal/PowerShell/CMD and may be under the impression that "nano" is a built-in command in Linux environments.

nano, however, is an optional package in Linux just as it is in Windows

@b-cpu commented on GitHub (Dec 3, 2023): I think he's asking for a native, built-in way to edit text files in Terminal/PowerShell/CMD and may be under the impression that "nano" is a built-in command in Linux environments. nano, however, is an optional package in Linux just as it is in Windows
claunia commented 2026-01-31 07:26:11 +00:00
Author
Owner
Copy Link

@plante-msft commented on GitHub (Dec 7, 2023):

@scanyard @b-cpu apologies for the late response to these comments. I am trying to gauge community interest in having one or more CLI text editors installed inbox and immediately available to Windows users.

Yes, nano is not a built-in command, but it does come installed by default on many distros - this is the behaviour I'm interested in gauging interest in for Windows.

I have opened up a Feature Exploration issue, and will be closing this one as a duplicate of that issue. If you have more feedback, please comment on there!

Closing as /dup #16438 .

@plante-msft commented on GitHub (Dec 7, 2023): @scanyard @b-cpu apologies for the late response to these comments. I am trying to gauge community interest in having one or more CLI text editors installed inbox and immediately available to Windows users. Yes, nano is not a built-in command, but it does come installed by default on many distros - this is the behaviour I'm interested in gauging interest in for Windows. I have opened up a Feature Exploration issue, and will be closing this one as a duplicate of that issue. If you have more feedback, please comment on there! Closing as /dup #16438 .
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-Feature Needs-Tag-Fix Needs-Triage
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#20860
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?