|
@@ -105,7 +105,7 @@ the following:</para>
|
|
|
set nocompatible
|
|
|
set backspace=2
|
|
|
syntax on
|
|
|
-set fileencodings=ucs-bom,utf-8,<replaceable>your-8-bit-charset</replaceable>
|
|
|
+<!-- set fileencodings=ucs-bom,utf-8,<replaceable>your-8-bit-charset</replaceable> -->
|
|
|
if (&term == "iterm") || (&term == "putty")
|
|
|
set background=dark
|
|
|
endif
|
|
@@ -119,7 +119,11 @@ vi-compatible manner. Remove the "no" if you want the old <command>vi</command>
|
|
|
behavior. The <emphasis>set backspace=2</emphasis> allows
|
|
|
backspacing over line breaks, autoindents and the start of insert. The
|
|
|
<emphasis>syntax on</emphasis> enables <command>vim</command>'s
|
|
|
-syntax highliting. The <emphasis>set fileencodings=...</emphasis> makes
|
|
|
+syntax highliting.
|
|
|
+<!-- XXX: the ascii-only files are considered to be in utf-8 - that's not what
|
|
|
+one expects . That's why fileencodings stuff is commented out for now
|
|
|
+
|
|
|
+The <emphasis>set fileencodings=...</emphasis> makes
|
|
|
<command>vim</command> capable of automatically detecting the character
|
|
|
set of the file being edited (replace
|
|
|
"<replaceable>your-8-bit-charset</replaceable>"
|
|
@@ -127,8 +131,8 @@ with the value appropriate for your country, e.g. iso-8859-15 in Italy).
|
|
|
This line is useful because bleeding-edge distributions
|
|
|
like Fedora Core use UTF-8, and conservative ones like Debian
|
|
|
use traditional 8-bit encodings for text files. If you have not
|
|
|
-passed the <option>--enable-multibyte</option> switch to the
|
|
|
-<command>./configure</command> command above, this line will not work.
|
|
|
+passed the <option>- -enable-multibyte</option> switch to the
|
|
|
+<command>./configure</command> command above, this line will not work. -->
|
|
|
Finally, the <emphasis>if</emphasis> statement with the
|
|
|
<emphasis>set background=dark</emphasis> corrects <command>vim</command>'s
|
|
|
guess about the background color of some terminal emulators. This gives the
|