<?xml version="1.0" encoding="windows-1252"?>
<node id="333878" title="Re: Learn vi/vim in 50 lines and 15 minutes" created="2004-03-04 09:48:37" updated="2005-07-07 15:27:42">
<type id="11">
note</type>
<author id="169744">
Abigail-II</author>
<data>
<field name="doctext">
&lt;blockquote&gt;
To edit a file with vi do:
&lt;code&gt;
vi file.txt
&lt;/code&gt;
&lt;/blockquote&gt;
This is a bit misleading. On many systems, if you do &lt;tt&gt;vi file.txt&lt;/tt&gt;, you do indeed edit the file with &lt;tt&gt;vi&lt;/tt&gt;,
and &lt;strong&gt;not&lt;/strong&gt; with &lt;tt&gt;vim&lt;/tt&gt;. You discuss &lt;tt&gt;vim&lt;/tt&gt;, and while &lt;tt&gt;vim&lt;/tt&gt; has many similarities 
with &lt;tt&gt;vi&lt;/tt&gt;, not everything you discuss will work in &lt;tt&gt;vi&lt;/tt&gt;. For instance, not on every system will the arrow keys work as expected in &lt;tt&gt;vi&lt;/tt&gt;. There's no syntax highlighting in &lt;tt&gt;vi&lt;/tt&gt;, nor does &lt;tt&gt;vi&lt;/tt&gt; have any perl hooks.
&lt;blockquote&gt;
It has 4 MODES.
&lt;/blockquote&gt;
That's just an opinion. One could also argue that &lt;tt&gt;vi&lt;/tt&gt; only has command mode. But some commands take
arbitrary long arguments. &lt;tt&gt;;-)&lt;/tt&gt;.
&lt;p&gt;
Abigail (using vi since 1984)</field>
<field name="root_node">
333737</field>
<field name="parent_node">
333737</field>
</data>
</node>
