> Because when you refactor the function/class name, it's never just one region ... the region is whatever you say it is: (mark-whole-buffer) (indent-regi

> Because when you refactor the function/class name, it's never just one region ... the region is whatever you say it is: (mark-whole-buffer) (indent-region) Or, most likely, something like: C-x h TAB I don't think that's particularly onerous. It's only a few lines of elisp to visit all the files in a tree and automatically format them. That said, it would probably be more sensible to modify whatever refactoring tool to be indentation aware, if it isn't already. Again, that's easy to do with elisp.