anchor.diff:  %% This refactoring replaces instances of the right-hand side of a macro definition by the corresponding
   %% left-hand side with necessary parameter substitutions. 
   %% </p>
  -%% <p> To apply this refactoring, first point the cursor to the macro definition against which candidate 
  +%% <p> Usage: to apply this refactoring, first point the cursor to the macro definition against which candidate 
   %%  expressions/candidates will be folded; then select <em> Fold Against Macro Definition </em> from the 
   %% <em> Refactor </em> menu; after that, Wrangler will search the current module for expressions/patterns
   %% which are instances of the right-hand side of the selected macro definition; and direct you through the 
   %% refactoring process.
   %% </p>
  +%%@spec fold_against_macro(FileName::filename(), Line::integer(), Col::integer(), SearchPaths::[dir()], TabWidth::integer()) ->
  +%%	      {error, string()} | {ok, [{{{integer(), integer()}, {integer(), integer()}}, syntaxTree()}]}
   -spec(fold_against_macro/5::(filename(), integer(), integer(), [dir()], integer()) ->
   	      {error, string()} | {ok, [{{{integer(), integer()}, {integer(), integer()}}, syntaxTree()}]}).
   fold_against_macro(FileName, Line, Col, SearchPaths, TabWidth) ->
       try_refactoring(refac_fold_against_macro, fold_against_macro, [FileName, Line, Col, SearchPaths, TabWidth]).
   
   
  +%% =============================================================================================
  +%% @doc Reorder the record fields in a record expression to be consistent with the record definiton.
  +%%<p>
  +%% Usage: point cursor to the record expression interested, then select <em>Normalise Record Expression</em> from <em>Refactor</em>.
  +%%</p>
  +%% @spec normalise_record_expr(FileName::filename(), Line::integer(), Col::integer(), ShowDefault::bool(), SearchPaths::[dir()], TabWidth::integer())
  +%%         -> {error, string()} | {ok, [filename()]}
   -spec(normalise_record_expr/6::(filename(), integer(), integer(), bool(), [dir()], integer()) -> {error, string()} | {ok, [filename()]}).
   normalise_record_expr(FileName, Line, Col, ShowDefault, SearchPaths, TabWidth) ->
       try_refactoring(refac_sim_expr_search, normalise_record_expr, [FileName, {Line, Col}, ShowDefault,SearchPaths, TabWidth]).
   
   
  -try_refactoring(Mod, Fun, Args) -> 
  -     try apply(Mod, Fun, Args)
  -     catch
  +%%@private
  +try_to_apply(Mod, Fun, Args, Msg) -> 
  +    try apply(Mod, Fun, Args)
  +    catch
    	throw:Error -> 
     	    Error;
  - 	_E1:_E2->
  -	     {error, "Wrangler failed to perform this refactoring, please report error to erlang-refactor@kent.ac.uk."}
  -     end.
  -
  +	  _E1:_E2->
  +	    {error, Msg}
  +    end.
  +
  +%%@private
  +try_refactoring(Mod, Fun, Args) ->
  +    Msg = "Wrangler failed to perform this refactoring, "
  +	"please report error to erlang-refactor@kent.ac.uk.",
  +    try_to_apply(Mod, Fun, Args, Msg).
  +
  +%%@private
  +try_inspector(Mod, Fun, Args) -> 
  +    Msg ="Wrangler failed to perform this functionality, "
  +	"please report error to erlang-refactor@kent.ac.uk.",
  +    try_to_apply(Mod, Fun, Args, Msg).
  +
  
positive.code: %% </p>
  %% <p>
  %% Usage: first check the SearchPaths specificed in the customisation page to make sure that the directory (or directories) specified is 
  %% the place where you want to search for duplicated code, then select <em> Detect Duplicated Code in Dirs </em> from the 
  %% <em> Refactor </em> sub-menu, Wrangler will then prompt to input the parameters.
  %% </p>
  %% @spec duplicated_code_in_dirs(FileNameList::[filename()|dir()], MinToks::string(), MinClones::string(),TabWidth:: integer()) -> {ok, string()}
  -spec(duplicated_code_in_dirs/4::([dir()], string(), string(), integer()) ->{ok, string()}).
  
negative.code: 	 new_macro_eclipse/6, rename_process_eclipse/6, rename_process_1_eclipse/5, 
  	 fun_to_process_eclipse/6, fun_to_process_1_eclipse/6]).
  
  -export([try_refactoring/3, try_inspector/3]).
  -include("../include/wrangler.hrl").
  
  %% ====================================================================================================
  %% @doc Rename a variable.
  %% <p> This refactoring has a local effect, i.e., it only affects the function clause in which the refactoring is initialized. 
  %% </p>
  %% <p> The following <em> side-conditions </em> (or <em>pre-conditions</em>) apply to this refactoring: 
  %% <li> The new variable name should not conflict with any of the declared variable names in the same scope;</li>
  