Flipping the Linux switch: Text editors for new users
First, a little experiment. What are the first three applications you think of when someone mentions text editors? If you can only answer Notepad, Notepad and Notepad, there's help for you yet.
True, the ubiquitous Notepad is a text editor. People who regularly use text editors often find Notepad quite limiting. That's why there are so many alternative text editors available for Windows.
Linux text editors are a different breed, more closely akin to the uber-editors that you can add to Windows (in fact, many Linux-based text editors have been ported to Windows and OS X). Sure, you can use them exactly the same way you use Notepad, if you want. But you can do so much more: programming in languages from C to XML, annotating documents with notes, and even collaborative editing.
We find ourselves using text editors more with Linux than with Windows. Not only because they're more powerful, but because they are life savers when we have a configuration file we need to edit by hand.
If you've looked at Linux text editors at all, you've found there is a battle raging that's just as passionate as the GNOME or KDE battle. The two text editors in question, Vi and Emacs, are powerful, extensible, and highly configurable. They've also got a steep learning curve for the new Linux user who just wants to tweak a setting in a config file, or create a simple document.
Have no fear. There are plenty of text editors out there that are powerful enough for the average user, and user-friendly to boot.
The minimalist: nano
nano is a small text-based (launched from the command line) text editor. It's top on our list for many reasons. A clone of the older Pico editor, nano can be used to easily view and edit files if, for whatever reason, your graphical server fails to start. We find ourselves using it for other tasks too, however. Sometimes it's easier to navigate to a directory using the console, and open a document directly in nano. Though it has a unique set of commands (for instance, ctrl-W searches for character strings) it is still easy to use, and help prompts are prominently displayed.
Launch nano in a terminal by typing nano <FILENAME> at the prompt.
We'd recommend every new user install nano, if it's not installed by default with your distribution.

The workaholic: Geany
Geany is a graphical application designed to be lightweight, and install with only the GTK2 runtime libraries as a dependency (this allows it to also run on Windows and Mac). Though its target users are the programming set, we will admit to using Geany for drafting many of the posts we write. It's clean, quick, and has tabbed file management.
If you are looking for something to edit code on, Geany has you covered. It supports a virtual terminal emulator, code folding and code completion, and syntax highlighting. For note takers and data freaks, there's a scribble board, and a status bar that records events such as document saves.

The reliable: gedit
gedit is the official text editor of the GNOME desktop environment. Though not the most glamorous of text editors, we find ourselves using it a lot. It has the basic features one would expect -- spell check, word count and search and replace. Its features can be extended with plugins. Since it is installed with the GNOME desktop, some people have no need to look any further than gedit.
If you prefer KDE, and do a lot of text editing, we'd recommend looking beyond the standard Kate or Kwrite applications. Where they do work in a pinch, Kate lacks some default features (such as word count) that we've come to expect.

The teacher: Cream
Cream is interesting, because it's more a set of nicely designed macros than a full-fledged text editor. It is a descendant of the Vi/Vim editors. Cream puts a familiar look on the Vim editor, making it accessible to new users. Basic features include spell check, bookmarks, code folding, and find and replace. Advanced features allow for different keyboard mappings, text color themes, and word completion. Ready to try your hand at Vim? You can easily toggle between Vi, Vim, and Cream behavior modes.
This is by far the most powerful editor we've recommended thus far, and the numerous features are likely overkill for many. If you're interested in learning more about how Vim works, or need its functionality but don't need the learning curve, Cream is a good choice.
Cream is available for other platforms, as well.

Plays well with others: Gobby
Gobby is a collaborative text editor. (It is also available for Windows, OS X and UNIX.) It connects computers on a network through an encrypted channel. It allows for the creation of multiple documents, dragging and dropping of documents, and has an IRC-style chat interface, so you can discuss any changes in real-time. Originally designed for programming collaboration, group editing of other types of documents is also possible. It's a neat application for offices that have a mix of software platforms.

You may rarely use a text editor, and decide gedit (or your desktop environment's counterpart) is all you need. You may use one daily, and prefer something a little more robust. You may even already use your chosen Linux text editor in Windows. How easy was that?












Comments
12
Subscribe to commentsWingJan 13th 2008 7:43PM
The thing I'm interested in is a good text editor that works in widescreen. I'm thinking about getting an ultraportable and height is a scarce commodity on those things. What's the best editor that takes advantage of extra width to compensate for the limited height?
thethirdmooseJan 13th 2008 7:48PM
What about vi and emacs?
PeterJan 13th 2008 8:08PM
If you're comfortable with vi or emacs, you made the switch to Linux a long time ago. I suffered with vi for a while before switching to nano. It's FAR superior for basic conf file editing.
alex danteJan 14th 2008 12:07AM
If you're using GNOME, I recommend checking out Scribes, a text/xml editor that aims to reduce repetition of entry as much as possible.
http://scribes.sourceforge.net/features.html
JohnJan 14th 2008 4:44AM
I started text editing with a Z80 Kaypro II, I regularly (but not exclusively) use "joe" because I still have the Wordstar commands in my blood. ^Kx
lefty.cruppsJan 14th 2008 1:31PM
on Linux, check out Kate further. It has multi-files (not quite tabs, but a list on the left) and the ability to open and run a Terminal from within; it also supports syntax highlighting for coders, and a lot of other great features. Of course its powerful -- its a part of KDE! Keep your GEdit.
HuwJan 14th 2008 9:55AM
GEdit has syntax highlighting too.
kingkool68Jan 14th 2008 11:01AM
What is everyone's favorite for HTML/CSS/JavaScript editing?
Kristin ShoemakerJan 14th 2008 12:38PM
I like Bluefish, or Quanta... Found them both nifty in different ways. I haven't used either in a while, and both look like they've added some nifty features.
Karl O. PincJan 14th 2008 2:07PM
I fail to understand why emacs is considered to have a "steep learning curve". There is one and only one thing to remember: hold down the control key and press the X key, keep the control key down and press the C key. That stops emacs.
Otherwise emacs is entirely painless. You type "emacs filename" to edit a file. The arrow keys do what you expect, the backspace key works, whatever you type is put into the file where the cursor is. When your done you hold down the control key and press XC and emacs asks if you want to save the file. What's so hard?
thethirdmooseJan 14th 2008 6:54PM
I agree
vi is also easy to use
i to edit
:wq to save and quit
angrykeyboarderJan 15th 2008 2:44AM
Kate rules. GEdit is #2. Cream is a dressed up Vim. And Vim and Emacs are for uber-nerds.
Lastly, for quick editing of config files, I vote for Nano.
I shouldn't have to read a book just to figure out how to use a text editor.