Update for mark, sorcerer, vylight. Removed syntax for C files (which was the

base for pd_opl)

doc/mark.txt

@@ -40,23 +40,35 @@ RELATED WORKS								     *
 - http://vim.wikia.com/wiki/Highlight_multiple_words offers control over the
   color used by mapping the 1-9 keys on the numeric keypad, persistence, and
   highlights only a single window. 
+- highlight.vim (vimscript #1599) highlights lines or patterns of interest in
+  different colors, using mappings that start with CTRL-H and work on cword. 
 
 ==============================================================================
 USAGE								  *mark-usage*
 
 HIGHLIGHTING						   *mark-highlighting*
 						     *<Leader>m* *v_<Leader>m*
-<Leader>m		Mark or unmark the word under the cursor, similar to
-			the |star| command. 
+<Leader>m		Mark the word under the cursor, similar to the |star|
+			command. The next free highlight group is used. 
+			If already on a mark: Clear the mark, like
+			|<Leader>n|. 
 {Visual}<Leader>m	Mark or unmark the visual selection. 
 						     *<Leader>r* *v_<Leader>r*
-<Leader>r		Manually input a regular expression to highlight. 
+<Leader>r		Manually input a regular expression to mark. 
 {Visual}<Leader>r	(Based on the visual selection.) 
+
 			In accordance with the built-in |star| command,
 			all these mappings use 'ignorecase', but not
 			'smartcase'. 
 								   *<Leader>n*
-<Leader>n		Clear the mark under the cursor / all marks. 
+<Leader>n		Clear the mark under the cursor.
+			If not on a mark: Clear all marks. 
+
+			Note: Marks that span multiple lines are not detected,
+			so the use of <Leader>n on such a mark will
+			unintentionally remove all marks! Use
+			{Visual}<Leader>r or :Mark {pattern} to clear
+			multi-line marks. 
 								       *:Mark*
 :Mark {pattern}		Mark or unmark {pattern}. 
 			For implementation reasons, {pattern} cannot use the
@@ -119,13 +131,14 @@ You may define your own colors or more than the default 6 highlightings in
 your vimrc file (or anywhere before this plugin is sourced), in the following
 form (where N = 1..): >
     highlight MarkWordN ctermbg=Cyan ctermfg=Black guibg=#8CCBEA guifg=Black
-<
+Higher numbers always take precedence and are displayed above lower ones. 
+
 The search type highlighting (in the search message) can be changed via: >
     highlight link SearchSpecialSearchType MoreMsg
-<
+<								 *g:mwHistAdd*
 By default, any marked words are also added to the search (/) and input (@)
 history; if you don't want that, remove the corresponding symbols from: >
-    let g:mwHistAdd = "/@"
+    let g:mwHistAdd = '/@'
 <
 You can use different mappings by mapping to the <Plug>Mark... mappings before
 this plugin is sourced. To remove the default overriding of * and #, use: >
@@ -164,6 +177,32 @@ http://vim.wikia.com/wiki/Highlight_multiple_words:
 ==============================================================================
 HISTORY								*mark-history*
 
+2.4.4	18-Apr-2011
+- BUG: Include trailing newline character in check for current mark, so that a
+  mark that matches the entire line (e.g. created by V<Leader>m) can be
+  cleared via <Leader>n. Thanks to ping for reporting this. 
+- FIX: On overlapping marks, mark#CurrentMark() returned the lowest, not the
+  highest visible mark. So on overlapping marks, the one that was not visible
+  at the cursor position was removed; very confusing! Use reverse iteration
+  order.  
+- FIX: To avoid an arbitrary ordering of highlightings when the highlighting
+  group names roll over, and to avoid order inconsistencies across different
+  windows and tabs, we assign a different priority based on the highlighting
+  group. 
+
+2.4.3	16-Apr-2011
+- Avoid losing the mark highlightings on :syn on or :colorscheme commands.
+  Thanks to Zhou YiChao for alerting me to this issue and suggesting a fix. 
+- Made the script more robust when somehow no highlightings have been defined
+  or when the window-local reckoning of match IDs got lost. I had very
+  occasionally encountered such script errors in the past. 
+- Made global housekeeping variables script-local, only g:mwHistAdd is used
+  for configuration. 
+
+2.4.2	14-Jan-2011 (unreleased)
+- FIX: Capturing the visual selection could still clobber the blockwise yank
+  mode of the unnamed register. 
+
 2.4.1	13-Jan-2011
 - FIX: Using a named register for capturing the visual selection on
   {Visual}<Leader>m and {Visual}<Leader>r clobbered the unnamed register. Now