Как редактировать файл через консоль windows

2021 UPDATE

As @phuclv has mentioned in comments, I want to emphasize that there is a tool that actually works great on Windows 64 bit too! It’s called Micro and fortunately, it is quite feature-rich, regularly updated and alive.

To install it, you only need to download the latest version’s 64bit.zip file from here, and then unzip it somewhere and add its path to your PATH. No dependencies or external files are needed — just the binary and you’re done.

Quick Start:

• Just type micro to create and edit a new text file.
• Type micro <filename> to start editing an already-made file.
• To save: ctrl + s
• To see a list of keybindings: alt + g
• To quit: ctrl + q

Some Exciting Features:

• Select text easily (using the shift key, or even using your mouse!), and then copy, cut, paste or delete the selected text using the same keybindings common in your operating system(e.g. ctrl + c for copy on Windows).
• Supporting so many common keybindings, e.g. ctrl + d to duplicate a line, or activate multiple curser mode and etc.
• Undo / Redo
• Syntax Highlighting (for more than 130 programming languages)
• Plugin System
• Typed Commands (instead of using keybindings)
• …

A tip on using Micro for VSCode users:

Since both VSCode and Micro try to support all common keybindings, you’ll probably have a lot of conflicting keybindings between them when using Micro inside the VSCode’s embedded CMD/PowerShell terminal. For instance, to quit Micro, you will have to use ctrl + q while it is the VSCode’s keybinding for the «Quick Open View» command.

But no worries! Micro also supports «Typed Commands» which allow you to control the editor using commands instead of keybindings. So you can type commands and you’re fine to use Micro on VSCode as well. However, there’s still a tiny problem. To enable «command mode» on Micro, you have to use ctrl + e, which is also a keybinding of VSCode for the «Go To File…» command. So you have to change the ctrl + e keybinding either on VSCode or on Micro to get rid of this conflict and then you’re all set.

Personally, I preferred to change Micro’s ctrl + e. Here are the steps from the documentation to change it to ctrl + w (or whatever else non-conflicting keybinding of your own liking) on a Windows machine:

1. Open %userprofile%/.config/micro/bindings.json with any editor.
2. Add this line to the end of the JSON: "Ctrl-w": "CommandMode"
3. Save.
   Now to enter command mode, press ctrl + w and type your commands (e.g.: quit, save, open, etc).

2021 UPDATE

As @phuclv has mentioned in comments, I want to emphasize that there is a tool that actually works great on Windows 64 bit too! It’s called Micro and fortunately, it is quite feature-rich, regularly updated and alive.

To install it, you only need to download the latest version’s 64bit.zip file from here, and then unzip it somewhere and add its path to your PATH. No dependencies or external files are needed — just the binary and you’re done.

Quick Start:

• Just type micro to create and edit a new text file.
• Type micro <filename> to start editing an already-made file.
• To save: ctrl + s
• To see a list of keybindings: alt + g
• To quit: ctrl + q

Some Exciting Features:

• Select text easily (using the shift key, or even using your mouse!), and then copy, cut, paste or delete the selected text using the same keybindings common in your operating system(e.g. ctrl + c for copy on Windows).
• Supporting so many common keybindings, e.g. ctrl + d to duplicate a line, or activate multiple curser mode and etc.
• Undo / Redo
• Syntax Highlighting (for more than 130 programming languages)
• Plugin System
• Typed Commands (instead of using keybindings)
• …

A tip on using Micro for VSCode users:

Since both VSCode and Micro try to support all common keybindings, you’ll probably have a lot of conflicting keybindings between them when using Micro inside the VSCode’s embedded CMD/PowerShell terminal. For instance, to quit Micro, you will have to use ctrl + q while it is the VSCode’s keybinding for the «Quick Open View» command.

But no worries! Micro also supports «Typed Commands» which allow you to control the editor using commands instead of keybindings. So you can type commands and you’re fine to use Micro on VSCode as well. However, there’s still a tiny problem. To enable «command mode» on Micro, you have to use ctrl + e, which is also a keybinding of VSCode for the «Go To File…» command. So you have to change the ctrl + e keybinding either on VSCode or on Micro to get rid of this conflict and then you’re all set.

Personally, I preferred to change Micro’s ctrl + e. Here are the steps from the documentation to change it to ctrl + w (or whatever else non-conflicting keybinding of your own liking) on a Windows machine:

1. Open %userprofile%/.config/micro/bindings.json with any editor.
2. Add this line to the end of the JSON: "Ctrl-w": "CommandMode"
3. Save.
   Now to enter command mode, press ctrl + w and type your commands (e.g.: quit, save, open, etc).

cd desktop

notepad filename.txt

type filename.txt

type geekbits.txt

Published by

Problem Formulation

Given is a text file, say my_file.txt. How to modify its content in your Windows command line working directory?

I’ll start with the most direct method to solve this problem in 90% of cases and give a more “pure” in-terminal method afterward.

Method 1: Using Notepad

The easiest way to edit a text file in the command line (CMD) on your Windows machine is to run the command notepad.exe my_text_file.txt, or simply notepad my_text_file.txt, in your cmd to open the text file with the visual editor Notepad.

notepad.exe my_file.txt

You can also skip the .exe prefix in most cases:

notepad my_text_file.txt

Now, you may ask:

💡 Is Notepad preinstalled in any Windows installation? The answer is: yes! Notepad is a generic text editor to create, open, and read plaintext files and it’s included with all Windows versions.

Here’s how that looks on my Win 10 machine:

When I type in the command notepad.exe my_text_file.txt, CMD starts the Notepad visual editor in a new window.

I can then edit the file and hit CTRL + S to save the new contents.

But what if you cannot open a text editor—e.g. if you’re logged into a remote server via SSH?

Method 2: Pure CMD Approach

If you cannot open Notepad or other visual editors for some reason, a simple way to overwrite a text file with built-in Windows command line tools is the following:

• Run the command echo 'your new content' > my_file.txt to print the new content using echo and pipe the output into the text file my_text_file.txt using >.
• Check the new content using the command type my_text_file.txt.

C:\Users\xcent\Desktop>echo 'hello world' > my_file.txt
C:\Users\xcent\Desktop>type my_file.txt
'hello world'

Here’s what this looks like on my Windows machine, where I changed my_file.txt to contain the text 'hello world!':

This is a simple and straightforward approach to small changes. However, if you have a large file and you just want to edit some minor details, this is not the best way.

Method 3: Change File Purely In CMD (Copy Con)

If you need a full-fledged solution to edit potentially large files in your Windows CMD, use this method! 👇

To create a new file in Windows command prompt, enter copy con followed by the target file name (copy con my_file.txt). Then enter the text you want to put in the file. To end and save the file, press Ctrl+Z then Enter or F6 then Enter.

copy con my_file.txt

How this looks on my Win machine:

A couple of notes:

💡 Info: To edit an existing file, display the text by using the type command followed by the file name. Then copy and paste the text into the copy con command to make changes. Be careful not to make any typos, or you’ll have to start over again. Backspace works if you catch the mistake before pressing Enter. Note that this method may not work in PowerShell or other command line interfaces that don’t support this feature.

Method 4: If you SSH’d to a Unix Machine

Of course, if you have logged in a Unix-based machine, you don’t need to install any editor because it comes with powerful integrated editors such as vim or emacs.

One of the following three commands should open your file in a terminal-based editing mode:

vim my_text_file.txt
vi my_text_file.txt
emacs my_text_file.txt

You can learn more about Vim here.

Summary

To edit a file.txt in the command line, use the command notepad file.txt to open a graphical editor on Windows.

If you need a simple file edit in your terminal without a graphical editor and without installation, you can use the command echo 'new content' > file.txt that overwrites the old content in file.txt with new content.

If you need a more direct in-CMD text editor run copy con file.txt to open the file in editing mode.

If you’re SSH’d into a Unix machine, running the Vim console-based editor may be the best idea. Use vim file.txt or vi file.txt to open it.

Feel free to join our email coding academy (it’s free):

👉 Recommended: How to Edit a Text File in PowerShell (Windows)

In linux i’m a fun of Nano or vim, i used to use nano and now vim, and they are really good choices. There is a version for windows. Here is the link https://nano-editor.org/dist/win32-support/

However more often we need to open the file in question, from the command line as quick as possible, to not loose time. We can use notepad.exe, we can use notepad++, and yea, we can use sublim text. I think there is no greater then a lightweight, Too powerful editor. Sublime text here. for the thing, we just don’t want to get out of the command line, or we want to use the command line to be fast. and yea. We can use sublime text for that. it contain a command line that let you quickly open a file in sublime text. Also there is different options arguments you can make use of. Here how you do it.

First you need to know that there is subl.exe. a command line interface for sublim.

1-> first we create a batch file. the content is

@ECHO OFF

"C:\Program Files\Sublime Text 3\subl.exe" %*

We can save that wherever we want. I preferred to create a directory on sublime text installation directory. And saved there the batch file we come to write and create.

(Remark: change the path above fallowing your installation).

2-> we add that folder to the path system environment variable. and that’s it.

or from system config (windows 7/8/10)

then:

then:

then we copy the path:

then we add that to the path variable:

too quick!

launch a new cmd and now you’ve got subl command working well!

to open a file you need just to use subl command as fellow:

subl myfileToOpen.txt

you can also use one of the options arguments (type —help to see them as in the image above).

Also note that you can apply the same method with mostly any editor of your choice.