anchor.diff:  %% a process name in a message, it would be help the refactoring process to select the process name from expressions, such as 
   %% registration expressions, where it is easier for Wrangler to infer that the atom is a process name.</li>
   %% </p>
  +%% <p> Usage: To apply this refactoring, point the cursor to the process name, then select
  +%% <em> Rename a Process </em> from the  <em> Refactor </em> menu, after that, Wrangler will prompt
  +%% to enter the new process name in the mini-buffer. 
  +%% </p>
   %% @spec rename_process(FileName::filename(), Line::integer(), Col::integer(),NewName::string(), SearchPaths::[dir()], TabWidth:: integer()) ->
   %%     {error, string()} | {undecidables, string()}| {ok, [filename()]}
   -spec(rename_process/6::(filename(), integer(), integer(), string(), [dir()], integer()) ->
  
positive.code: %% <li> In the case that the function is imported by another module, then <code>f/n</code> 
  %% should not be already in scope (either defined or imported) in that module. </li>
  %% </p>
  %% <p> Usage: to apply this refactoring, point the cursor to the parameter which is going to be the first 
  %% element of the tuple, then select <em> Tuple Function Arguments </em> from the <em> Refactor </em> sub-menu, 
  %% after that, Wrangler will prompt to enter the number of parameters to include into the tuple in the minibuffer.
  %% </p>
  %% @spec tuple_funpar(FileName::filename(), StartLoc::pos(), EndLoc::pos(), SearchPaths::[dir()], TabWidth:: integer())
  %% -> {error, string()} | {ok, [filename()]}
  -spec(tuple_funpar/5::(filename(), pos(), pos, [dir()], integer()) ->
  	     {error, string()} | {ok, [filename()]}).
  
  tuple_funpar(FileName, StartLoc, EndLoc,SearchPaths, TabWidth) ->
      try_refactoring(refac_tuple, tuple_funpar, [FileName, StartLoc, EndLoc, SearchPaths, TabWidth]).
  
  
  
  tuple_funpar_1(FileName, StartLoc, EndLoc,SearchPaths, TabWidth) ->
      try_refactoring(refac_tuple, tuple_funpar_1, [FileName, StartLoc, EndLoc, SearchPaths, TabWidth]).
  
  
  %%@private
  %% @spec tuple_funpar_eclipse(FileName::filename(), Line::integer(), Col::integer(), Number::string(), SearchPaths::[dir()], TabWidth:: integer()) -> term()
  
  -spec(tuple_funpar_eclipse/5::(filename(), pos(), pos, [dir()], integer()) ->
  	     {error, string()} | {ok, [{filename(), filename(), string()}]}).
  
  tuple_funpar_eclipse(FileName, StartLoc, EndLoc, SearchPaths, TabWidth) ->
      try_refactoring(refac_tuple, tuple_funpar_eclipse, [FileName, StartLoc, EndLoc, SearchPaths, TabWidth]).
  
  
  tuple_funpar_eclipse_1(FileName, StartLoc, EndLoc, SearchPaths, TabWidth) ->
      try_refactoring(refac_tuple, tuple_funpar_eclipse_1, [FileName, StartLoc, EndLoc, SearchPaths, TabWidth]).
  
  
  
  %%=========================================================================================
  %% @doc From tuple to record representation.
  %%  NOTE: this refactoring is still in an experimental stage.
  %% <p>
  
negative.code:     try_refactoring(refac_rename_var, rename_var_eclipse, [FileName, Line, Col, NewName, SearchPaths, TabWidth]).
  
  %%=========================================================================================
  %% @doc Rename a function.
  %% <p>
  %% When renaming an exported function, this refactoring has a global effect, that is, 
  %% it affects all those modules in which this function is imported/used.
  