June 26, 2008 at 11:45 Linux Text Editors (Part 1): vi, Gedit, Kate
Why do we need text editors, probably everyone knows: you can edit configuration files in them, you can create or correct a script in them, and you can also browse README-file corny. There are not so few text editors for Linux. And most of them can be customized for most arising tasks.
vi Old
Leader vi (or one of its variations, such as Vim or Elvis) is available on most * nix systems. If you are a system administrator and run from one * nix system to another, then you have a direct path to vi for work, macrosand so on. Once you learn keyboard shortcuts, control words, moving sections of text, or moving through large files, then vi will become efficient, fast, and predictable. Although vi does not have a GUI, but as for me php with highlighting in it looks very impressive.
Gedit and Kate
Gedit (Figure 1) is a small and lightweight text editor for GNOME. This editor is the default editor in Ubuntu. An excellent text editor with syntax highlighting scripts and programming languages. It is extensible through plugins (Fig. 2) and is most effective for most tasks. Fig. 1 GEdit text editor Fig. 2 GEdit text editor - plugins setup
I have a special love for GEdit - this is my most used and favorite editor. To configure GEdit correctly, follow the link and follow the instructions.
My GEdit looks like this: Fig . 3 GEdit text editor - configured. You can also run Kate (KDE Advanced Text Editor) under GNOME . With a simple command, you can install a package that will add some additional functionality. Kate’s interface is a bit livelier than Gedit’s (Fig. 4), and to enable tabs between documents, you need to activate this feature by connecting the appropriate plug-in. But Kate is more customizable than Gedit. Fig. 4 Kate text editor
That's all for today. In the next part of the article (or in several articles) the following text editors will be considered: TEA, Emacs, Leafpad, Mousepad, Medit, and SciTE.
Original ->
vi Old
Leader vi (or one of its variations, such as Vim or Elvis) is available on most * nix systems. If you are a system administrator and run from one * nix system to another, then you have a direct path to vi for work, macrosand so on. Once you learn keyboard shortcuts, control words, moving sections of text, or moving through large files, then vi will become efficient, fast, and predictable. Although vi does not have a GUI, but as for me php with highlighting in it looks very impressive.
Gedit and Kate
Gedit (Figure 1) is a small and lightweight text editor for GNOME. This editor is the default editor in Ubuntu. An excellent text editor with syntax highlighting scripts and programming languages. It is extensible through plugins (Fig. 2) and is most effective for most tasks. Fig. 1 GEdit text editor Fig. 2 GEdit text editor - plugins setup
I have a special love for GEdit - this is my most used and favorite editor. To configure GEdit correctly, follow the link and follow the instructions.
My GEdit looks like this: Fig . 3 GEdit text editor - configured. You can also run Kate (KDE Advanced Text Editor) under GNOME . With a simple command, you can install a package that will add some additional functionality. Kate’s interface is a bit livelier than Gedit’s (Fig. 4), and to enable tabs between documents, you need to activate this feature by connecting the appropriate plug-in. But Kate is more customizable than Gedit. Fig. 4 Kate text editor
sudo apt-get install kate-plugins
That's all for today. In the next part of the article (or in several articles) the following text editors will be considered: TEA, Emacs, Leafpad, Mousepad, Medit, and SciTE.
Original ->
