Download a code and text editor for Windows

Spot the files that call for plain text

A configuration, a script and a log can all be readable in the same editor while obeying very different rules. Review the extension and documentation of the program involved before you alter a value. A document meant to carry styles, a table of contents or pagination is better suited to a word processor. Notepad++ will not turn a DOCX file into editable text with its layout left intact. The other way around, saving a configuration from an office tool can slip in an unsuitable structure. The software you pick must therefore fit the actual content of the file and the way it will be read after editing.

Narrow the search before changing many files

A search can aim at one document, at open tabs or at a set of files within a folder. Set this scope before you carry out a replacement. The same word may surface in a comment, in a value and in a variable name, each with a different role. Regular expressions let you pin down patterns, but their symbols carry a specific meaning. Begin by looking over the matches found and trying the change on a small set. A backup or a version history makes returning to the previous state easier. Macros can repeat actions, as long as the line structure matches the one used while preparing them.

Verify encoding and line endings

How a file looks depends on how its bytes are read. If the accents come out wrong, work out the encoding before you manually replace the visible characters. Reading a file with another encoding and converting its contents are two separate operations. Line endings also have to meet what the receiving program expects. After saving, open a sample in the application that truly consumes the file. This check surfaces a change that stayed invisible in the editor. For a configuration, also keep the expected permissions and location; a correct file in the wrong place will not necessarily be used by the program in question.

Set the editor’s place in your workflow

Notepad++ supplies an editing environment, but the compiler, interpreter or validation tools depend on the language and the project. Pin down these elements instead of expecting the editor to run every file on its own. Extensions can round out how it works; check their architecture and usefulness before installing them. On a freshly configured computer, the tools after installing Windows selection places the editor among the everyday tools. If the software license weighs on your decision, the open source software for Windows selection lets you look at other tasks covered by open projects. These paths round out the editor's choice without turning a plain text tool into an office suite or a universal development environment.

Frequently asked questions