spw/perltidy-region: use process-environment rather than setenv

1 files changed, 9 insertions, 10 deletions

diff --git a/.emacs.d/init.el b/.emacs.d/init.el
index 89644aa1..b3e79bef 100644
--- a/.emacs.d/init.el
+++ b/.emacs.d/init.el
@@ -5620,16 +5620,15 @@ We don't use the FILES parameter in the entry for \"d\" in
 
 (defun spw/perltidy-region (begin end)
   (interactive "r")
-  (let ((perltidy-env (getenv "PERLTIDY")))
-    (setenv "PERLTIDY"
-            (or (concat (expand-file-name
-                         (locate-dominating-file
-                          (buffer-file-name)
-                          ".perltidyrc")) ".perltidyrc")
-                perltidy-env))
-    (shell-command-on-region begin end "perltidy -q" nil t)
-    (font-lock-ensure)
-    (setenv "PERLTIDY" perltidy-env)))
+  (let* ((dominating (locate-dominating-file default-directory ".perltidyrc"))
+	 (process-environment
+	  (if dominating
+	      (cons (format "PERLTIDY=%s"
+			    (expand-file-name ".perltidyrc" dominating))
+		    process-environment)
+	    process-environment)))
+    (shell-command-on-region begin end "perltidy -q" nil t))
+  (font-lock-ensure))
 
 ;; an older version of this would use the region if it's active, but that
 ;; rarely produces good results -- perltidy would get the indentation wrong