From 75a4a592e5ccda30715f93563d741b83e0dcf39e Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Mon, 25 Apr 2011 13:37:00 +0000 Subject: Slackware 13.37 Mon Apr 25 13:37:00 UTC 2011 Slackware 13.37 x86_64 stable is released! Thanks to everyone who pitched in on this release: the Slackware team, the folks producing upstream code, and linuxquestions.org for providing a great forum for collaboration and testing. The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. Please consider supporting the Slackware project by picking up a copy from store.slackware.com. We're taking pre-orders now, and offer a discount if you sign up for a subscription. As always, thanks to the Slackware community for testing, suggestions, and feedback. :-) Have fun! --- slackbook/html/vi-configuration.html | 96 ++++++++++++++++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 slackbook/html/vi-configuration.html (limited to 'slackbook/html/vi-configuration.html') diff --git a/slackbook/html/vi-configuration.html b/slackbook/html/vi-configuration.html new file mode 100644 index 00000000..e37b86dd --- /dev/null +++ b/slackbook/html/vi-configuration.html @@ -0,0 +1,96 @@ + + + + +vi Configuration + + + + + + + + + +
+ + + + + + + + + + +
Slackware Linux Essentials
PrevChapter 16 ViNext
+ +
+
+ +
+

16.6 vi +Configuration

+ +

Your vi clone of choice can be configured in several +ways.

+ +

A variety of commands can be entered while in command mode to set up vi just how you like it. Depending on your editor, you can enable +features to make programming easier (like syntax hilighting, auto-indenting, and more), +set up macros to automake tasks, enable textual substitutions, and more.

+ +

Almost all of these commands can be put into a configuration file in your home +directory. elvis expects a .exrc file, +while vim expects a .vimrc file. Most +of the setup commands that can be entered in command mode can be placed in the +configuration file. This includes setup information, textual substitutions, macros, and +more.

+ +

Discussing all these options and the differences between the editors is quite an +involved subject. For more information, check out the man page or web site for your +preferred vi editor. Some editors (like vim) have extensive help within the editor that can be accessed with +the :help command, or something similar. You can also check out the +O'Reilly book Learning the vi Editor by +Lamb and Robbins.

+ +

Many common programs in Linux will load up a text file in vi +by default. For example, editing your crontabs will start up vi +by default. If you do not like vi and would like another editor +to be started instead, all you need to do is set the VISUAL +environment variable to the editor you prefer. For information on setting environment +variables, see the section called Environment Variables in Chapter 8. If you want to make +sure that your editor will be the default every time you login, add the VISUAL setting to +your .bash_profile or .bashrc +files.

+
+ +
+
+ + + + + + + + + + + + +
PrevHomeNext
Quitting viUpVi Keys
+
+ + + -- cgit v1.2.3