[mapserver-commits] r8197 - trunk/docs/development/editing

[svn at osgeo.org]

Author: hobu
Date: 2008-12-05 09:52:42 -0500 (Fri, 05 Dec 2008)
New Revision: 8197

Modified:
   trunk/docs/development/editing/vim.txt
Log:
no section numbers

Modified: trunk/docs/development/editing/vim.txt
===================================================================
--- trunk/docs/development/editing/vim.txt	2008-12-05 02:32:47 UTC (rev 8196)
+++ trunk/docs/development/editing/vim.txt	2008-12-05 14:52:42 UTC (rev 8197)
@@ -10,8 +10,6 @@
 :Date: $Date$
 :Last Updated: 2006/5/5
 
-.. sectnum::
-
 .. contents:: Table of Contents
     :depth: 2
     :backlinks: top
@@ -21,8 +19,10 @@
 
 vi (vim) resides in: /usr/share/vim/current (vim_root).
 
-Syntax definitions are in vim_root/syntax/\*.vim files. Linking file types to extensions is done in vim_root/ftdetect/\*.vim. (The the star denotes 
-the extension and would be replaced with map to define highlighting of Mapserver config files).
+Syntax definitions are in vim_root/syntax/\*.vim files. Linking file types to
+extensions is done in vim_root/ftdetect/\*.vim. (The the star denotes the
+extension and would be replaced with map to define highlighting of Mapserver
+config files).
 
 
 
@@ -37,8 +37,9 @@
 
 2. Register the syntax file in the custom filetype directory
 
-   If absent, create a new directory called ftdetect in vim_root (on Suse Linux: /usr/share/vim/current).
-   Create a new file called map.vim in ftdetect according to the example shown below:
+   If absent, create a new directory called ftdetect in vim_root (on Suse
+   Linux: /usr/share/vim/current). Create a new file called map.vim in
+   ftdetect according to the example shown below:
 
    ::
 
@@ -53,30 +54,40 @@
 Introduction
 ------------
 
-`Vim code folding <http://www.vim.org/htmldoc/usr_28.html>`__ can be an extremely handy way to simplify the task of editing complex MapServer mapfiles inside the Vim editor. A Vim command file called `*map_fold.vim*`_ is attached to this document, which defines a folding mode for mapfiles. This file also lives at http://iconocla.st/code/dot/map_fold.vim.
+`Vim code folding <http://www.vim.org/htmldoc/usr_28.html>`__ can be an
+extremely handy way to simplify the task of editing complex MapServer mapfiles
+inside the Vim editor. A Vim command file called `*map_fold.vim*`_ is attached
+to this document, which defines a folding mode for mapfiles. This file also
+lives at http://iconocla.st/code/dot/map_fold.vim.
 
 Installation
 ------------
 
-Global installation of new Vim filetypes is described in the `Vim syntax howto <http://mapserver.gis.umn.edu/docs/howto/vim-syntax-howto>`__. In Vim 6, you can copy *map_fold.vim* as-is to your *$VIMROOT/ftplugin/* directory, and it should more or less work.
+In Vim 6, you can copy *map_fold.vim* as-is to your *$VIMROOT/ftplugin/*
+directory, and it should more or less work.
 
-To use locally, create a *~/.vim/ftplugin* directory, copy *map_fold.vim* to it, and then add the following to your *~/.vimrc*:
+To use locally, create a *~/.vim/ftplugin* directory, copy *map_fold.vim* to
+it, and then add the following to your *~/.vimrc*:
 
 ::
 
   autocmd BufRead *.map set filetype=map
 
-`map_fold.vim`_ is totally compatible with the `map.vim`_ syntax highlighter, and their combined use is even recommended.
+`map_fold.vim`_ is totally compatible with the `map.vim`_ syntax highlighter,
+and their combined use is even recommended.
 
 Use
 ---
 
-The Vim `folding tutorial <http://www.vim.org/htmldoc/usr_28.html>`__ (at least the first two or three sections) is highly recommended. The Vim `folding reference <http://www.vim.org/htmldoc/fold.html>`__ may also be helpful.
+The Vim `folding tutorial <http://www.vim.org/htmldoc/usr_28.html>`__ (at
+least the first two or three sections) is highly recommended. The Vim `folding
+reference <http://www.vim.org/htmldoc/fold.html>`__ may also be helpful.
 
 Conclusion
 ----------
 
-Hope this helps! Please let me know if you find it useful, or if you find ways to improve it. Thanks!
+Hope this helps! Please let me know if you find it useful, or if you find ways
+to improve it. Thanks!
  
 Closing Remarks
 ===============