anchor.diff:  %% <li> The selected part must be a tuple.  </li>
   %% </p>
   %% <p> To apply this refactoring, highlight the tuple, which should be a function parameter,  
  -%% then select <em> From Tuple To Record </em> from <em> Refactor </em>, 
  +%% then select <em> From Tuple To Record </em> from <em> Refactor</em>, 
   %% Wrangler will then prompt to enter the record name and  the record field names.
   %% </p>
   %% @spec tuple_to_record(File::filename(),FLine::integer(),FCol::integer(),
   %%           LLine::integer(),LCol::integer(), RecName::string(),
   %%           FieldString::[string()], SearchPaths::[dir()], TabWidth:: integer()) ->  {error, string()} | {ok, [filename()]} 
   %% @end
  -%%-spec(tuple_to_record/9::(filename(), integer(), integer(), integer(), integer(), string(), [string()], [dir()], integer()) ->
  -%%	     {error, string()} | {ok, [filename()]}).
  -
  +-spec(tuple_to_record/9::(filename(), integer(), integer(), integer(), integer(), string(), [string()], [dir()], integer()) ->
  +	     {error, string()} | {ok, [filename()]}).
   tuple_to_record(File, FLine, FCol, LLine, LCol, RecName, FieldString, SearchPaths, TabWidth) ->
       try_refactoring(refac_tuple_to_record, tuple_to_record, [File, FLine, FCol, LLine, LCol, RecName,
   					  FieldString, SearchPaths, TabWidth]).
  
positive.code: %% </p>
  % @spec rename_mod_batch(OldNamePattern::string(), NewNamePattern::string(), 
  %%                        SearchPaths::[dir()], TabWidth:: integer())-> {ok, string()}| {error, string()}
  %%   
  %%-spec(rename_mod_batch/4::(string(), string(), [dir()], integer())->
  %%	     {ok, string()} | {error, string()}).
  rename_mod_batch(OldNamePattern, NewNamePattern, SearchPaths, TabWidth) ->
      try_refactoring(refac_batch_rename_mod, batch_rename_mod, [OldNamePattern, NewNamePattern, SearchPaths, TabWidth]).
  
  
negative.code: %% </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()) ->
  	       {error, string()} | {undecidables, string()} | {ok, [filename()]}).
  rename_process(FileName, Line, Col, NewName, SearchPaths, TabWidth) ->
      try_refactoring(refac_rename_process, rename_process, [FileName, Line, Col, NewName, SearchPaths, TabWidth]).
  
  
  %%@private
  -spec(rename_process_eclipse/6::(filename(), integer(), integer(), string(), [dir()], integer()) ->
  	       {error, string()} | {undecidables, string()} |  {ok, [{filename(), filename(), string()}]}).
  rename_process_eclipse(FileName, Line, Col, NewName, SearchPaths, TabWidth) ->
      try_refactoring(refac_rename_process, rename_process_eclipse, [FileName, Line, Col, NewName, SearchPaths, TabWidth]).
  
  %%@private
  -spec(rename_process_1_eclipse/5::(string(), string(), string(), [dir()], integer()) -> {ok, [{filename(), filename(), string()}]}).
  rename_process_1_eclipse(FileName, OldProcessName, NewProcessName, SearchPaths, TabWidth) ->
      try_refactoring(refac_rename_process, rename_process_1_eclipse, [FileName, OldProcessName, NewProcessName, SearchPaths, TabWidth]).
  
  %% =====================================================================================================
  %% @doc Introduce a macro to represent a syntactically well-formed expression/pattern or a sequence of expressions/patterns.
  %% <p> This refactoring allows the user to define a new macro to represent a expression/pattern or sequence 
  %% of expressions/patterns selected by the user, and replace the selected code with an application of the macro.
  %% Free variables within the selected code become the formal parameters of the macro definition.
  %% </p>
  