Choosing an editor

Which editor you use is largely a question of personal taste.

  • Do you want to use a mouse or other pointer, or do you want to use just the keyboard?
  • Do you need to type international characters, accents, and diacritical marks, or just ASCII?
  • How do you like to invoke commands? In some editors, you type a single character, in others, you press a keychord, and in yet others, you click a button or select an item from a menu.

One important distinction between the editors is whether they're text-based or graphical. Text-based editors are more flexible because you can use them in text mode, in a console window, remotely via telnet or qtalk, and so on; graphical editors tend to be friendlier and easier to use, but can run only in a graphical window.

If you start a graphical editor from the command line, you'll probably want to start it as a background process — by adding an ampersand (&) to the command line — so that you can continue to use the current window while the editor is still open. If you're using a text-based editor, start it as a foreground process by omitting the ampersand.

Neutrino includes these editors:

vi
A powerful, but somewhat cryptic text-based editor that you'll find in most — if not all — UNIX-style operating systems.

On Linux and Windows, the QNX Momentics Tool Suite features an Integrated Development Environment (IDE) that incorporates various specialized editors for creating C and C++ programs, buildfiles, and so on. For more information, see the IDE User's Guide .