How to Use the New Edit in Windows: A Complete, Practical Guide

Windows 11 is about to receive a tool that will delight those who live in the Bus Terminal: a lightweight text editor called Edit, designed to work directly from the command line. commands. Its proposal is minimalist, fast and without distractions, and is reminiscent of the classic experience of working with files from the console, but with a modern text-based interface.

If Notepad feels too heavy for you after adding advanced features (even with IA), Edit is just the opposite: a CLI editor to open, create and modify text without leaving PowerShell or of symbol of the system, simply typing edit or adding the name of the file you want to edit. It's perfect for administrators, developers, and anyone who prefers to navigate the console without loading a heavy graphical environment.

What is Edit and what makes it different?

Edit is a command-line text editor with a TUI (Text-based User Interface). This means that works in the Terminal with a visual text interface, includes keyboard-accessible menus and, unlike many classic CLI editors, also allows you to use the mouse to click on options or select text.

Microsoft has built it with a clear philosophy: to offer a default, modeless editor for 64-bit versions of Windows, with a very low barrier to entry for new users. The interface is simple but modern, with controls reminiscent of Visual Studio Code., although here everything runs within the Terminal and without the weight of a full editor.

Among its most striking features is its lightness: the binary occupies around 230 KB (less than 250 KB). It does not have syntax highlighting or tabs "as such", and it doesn't have a context menu either; however, it allows you to open multiple files at once within the same session, making it very useful for reviewing multiple documents in parallel.

Another point to note is that Edit is cross-platform at the code level: it is written in Rust, the popular memory-safe language. Microsoft itself has released its code under the MIT license. and encourages the community to explore, propose improvements, and contribute to its GitHub repository.

Install Edit on Windows

Microsoft will integrate Edit into future builds of Windows 11, so it will arrive natively with the system later. In the meantime, you can install the latest version with Winget, the official Windows package manager, with a single command in your Terminal.

winget install Microsoft.Edit

If you're working with an older version of Windows, or prefer to do it manually, you can get the tool from its GitHub repository in the releases section. The company is gradually rolling out Edit through the Windows Insider Program., so it may take a while for it to appear as the default component for all users.

Edit was unveiled at Microsoft Build, the developer event, and has been constantly evolving ever since. The decision to publish it as an open project in Rust makes it easier to audit and contribute to., and has even motivated experimental builds for other platforms such as macOS, BSD or Linux, as well as builds for ARM architectures.

Open and create files with Edit from the Terminal

The beauty of Edit is that it doesn't take you out of the console workflow. To launch it, just type edit and press Enter. If you add a file name, it will open directly for editing.; if that file doesn't exist, you can create it on the fly without changing context.

edit
edit <nombre-de-archivo.txt>

It is possible to pass multiple files in the same invocation if you need to compare them or switch between them. With a simple command you can load multiple log sources or different configuration files at once., which is very handy when you're looking for quick differences or implementing coordinated changes.

edit servidor.log errores.log configuracion.ini

Everything happens within Windows Terminal, with a very clear text-based interface. You can move with the keyboard or the mouse and you'll have accessible menus for the most common functions, without having to memorize exotic combinations.

TUI interface and essential keyboard shortcuts

Edit's text-based interface is straightforward and unadorned. You'll find the main actions in the menu, but each one comes with its own shortcut already configured, so you can You can do almost everything without lifting your hands from the keyboard or, if you find it more convenient, with mouse clicks.

To find and replace text, you have at hand Ctrl + F. Search supports "Match case", "Whole words", and "Regular expressions", covering most of the needs of professional console use. If you frequently inspect logs or configuration files, this combination will be especially useful.

When working with very long lines, you can activate line wrapping (Word Wrap) with Alt + Z. The on-screen folding prevents you from having to scroll horizontally. and helps you stay focused on the content, which is key when reviewing logs long or endless configuration strings.

Edit recognizes common shortcuts in the Windows ecosystem, such as Ctrl + Z to undo, Ctrl + V to stick or Ctrl + R associated with frequently used actions. There is no context menu or heavy interface: the experience is minimal and predictable., designed for frictionless entry, editing, and exit.

Although its interface may give the impression of supporting tabs, it does not work with traditional tabs. In practice it runs within the Terminal instance; However, you can open multiple files at once in a single editor session and navigate between them seamlessly.

When to Use Edit: Real-World Use Cases

Where Edit shines the most is in Terminal-centric workflows. If you manage systems, programs on a daily basis, or do support, Having an ultra-light editor at a command's reach speeds up routine tasks a lot.: open a log, correct a configuration value, such as edit the hosts file or compose a quick note without leaving the command line.

It works especially well with large files, such as application and service logs. Being a minimal and independent editor, it avoids the overload of a complete graphical environment and responds smoothly, even with large files that you want to browse and filter with the search.

If Notepad has evolved towards a more ambitious feature set, Edit claims simplicity. His proposal is deliberately sober for those who prefer "less is more" and value editing in the same place where they compile, deploy, or automate tasks.

Being written in Rust provides stability and memory security, reducing risks when handling data. In addition, its small size and open license make it ideal to integrate as a default tool. on 64-bit Windows installations without adding unnecessary weight to the system.

Project Philosophy: Why another CLI editor?

Microsoft identified a shortcoming in modern Windows installations: there was no default 64-bit command line editor that was lightweight, simple, and "home-made." The idea of ​​Edit is to offer a modeless editor with a low learning curve., accessible for both beginners and those who have mastered the Terminal.

Many existing modeless editors either did not offer first-party support for Windows or were too bulky to be included in every version of the operating system. That's why Edit was built from scratch., with a focus on speed, Terminal compatibility, and a precise and well-resolved feature set.

Open source repository and contributions

Edit is an open project and the company encourages the community to participate. The source code is available on GitHub under the MIT license., with the possibility of proposing changes, reporting incidents or suggesting new functions in the repository itself.

In addition to support for 64-bit Windows, the Rust foundation has led to builds that work on Linux and BSD systems, and even on macOS experimentally. There are also builds for ARM architectures, which anticipates a broad ecosystem as the community adopts it.

New Edit vs. the classic MS-DOS Editor

It's worth distinguishing between the new Edit and the historic "MS-DOS Editor" that many remember from the 90s. That utility launched a text-mode editor for ASCII files from the DOS command interpreter, with a specific syntax and its own switches. The modern Edit is another program, with different architecture and objectives, although both share a minimalist spirit and name.

For those nostalgic or those who maintain legacy environments, this was it invoking the MS-DOS Editor:

edit      <archivo> ]]

These were their most common parameters, re-explained in a current way:

• Path and file name: file ] opened one or more ASCII files; if they didn't exist, they were created, and if they were already created, they were displayed on the screen. Names could include wildcards such as * and ?, and multiple names were separated by spaces.
• /b: forced monochrome mode to display the editor in black and white, useful with monitors that did not render certain attributes well.
• /h: asked the editor to display as many lines as possible for the current monitor.
• /r: Loaded files in read-only mode, preventing accidental modifications.
• /s: forced the use of short names (8.3), something relevant in systems and utilities that did not accept long names.
• /: opened binary files by setting the line width to nnn characters, useful for quick inspections of non-textual data.
• /?: displayed help from the command prompt itself.

When opening the MS-DOS Editor you could press F1 to access the application's contextual help. If the monitor did not display the hotkeys correctly on the screen, it was recommended to start the editor with the /b switch to improve compatibility.

Two classic examples that will still be familiar to you because of their simplicity:

edit
edit newtextfile.txt

We repeat: the new Edit in Windows 11 is not the MS-DOS Editor. It shares a minimalist philosophy and console access, but it is a modern program., with mouse support, advanced search, and an updated TUI that lives inside Windows Terminal.

Availability, deployment and release pace

Microsoft has already confirmed that it will include Edit in upcoming builds of Windows 11, and in the meantime, it's making it easy to install via Winget or download from GitHub. The rollout through Windows Insider is gradual., so it will take some time for it to appear as the default command line editor on all stable installations.

The tool was introduced at Microsoft Build, and since then, the company has reiterated its commitment to its own 64-bit CLI editor. Its tiny size and open focus They fit with the idea of ​​distributing it widely without penalizing resources or complexity.

Practical tips for working faster

Get used to invoking Edit directly with the target file: for example, edit C:\\logs\\app.log. You will enter editing immediately and exit without any intermediate steps., ideal when you are in the middle of a maintenance or debugging session.

To dive into very long records or texts, combine Ctrl + F with the “Whole words” and “Match case” options. If you need complex patterns, turn on "Regular Expressions" and narrow your search down to precise fragments without leaving the Terminal.

When you encounter endless lines (URLs, connection strings, minified JSON), toggle line wrapping on or off with Alt + Z as it suits you. You will see the content adapted to the width of your console, which saves you from having to scroll sideways and break the reading rhythm.

Open multiple files at once if you need quick correlations: edit today.log yesterday.log config.ini. Being able to move between them without leaving the editor It saves you from launching and closing sessions and keeps your focus on the analysis.

The arrival of Edit brings back to Windows a fast and easy console text editor, with just the right amount of power for everyday use: advanced search (with regex), line wrapping and recognizable shortcuts, plus mouse control within a modern TUI. It's lightweight, open source, written in Rust, and built for 64-bit., is installed with Winget and will be integrated into Windows 11 as its rollout progresses; and while it's not the old MS-DOS Editor, it pays homage to it by bringing back the agility of editing directly from the Terminal.

Related article:

Access Notepad to edit configuration files from the Windows 11 installer

Isaac

Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.