Remove nonfunctional sudoedit filetype detection

With the removal of SUDO_COMMAND from the sudoedit environment, we're
dead in the water.

References: tpope#31

Author: tpope

README.markdown

@@ -17,7 +17,6 @@ include:
   [guard][].
 * `:SudoWrite`: Write a privileged file with `sudo`.
 * `:SudoEdit`: Edit a privileged file with `sudo`.
-* File type detection for `sudo -e` is based on original file name.
 * Typing a shebang line causes the file type to be re-detected.  Additionally
   the file will be automically made executable (`chmod +x`) after the next
   write.

doc/eunuch.txt

@@ -85,9 +85,6 @@ COMMANDS                                        *eunuch-commands*
 
 PASSIVE BEHAVIORS                               *eunuch-passive*
 
-File type detection for files edited with `sudoedit` and `sudo -e` happens
-based on the original file name, as found in $SUDO_COMMAND.
-
 If you type a line at the beginning of a file that starts with #! and press
 <CR>, The current file type will be re-detected.  This is implemented using a
 <CR> map.  If you already have a <CR> map, you can incorporate this behavior

plugin/eunuch.vim

@@ -279,21 +279,6 @@ command! -bar SudoWrite
       \ write!
 endif
 
-function! s:SudoEditInit() abort
-  let files = split($SUDO_COMMAND, ' ')[1:-1]
-  if len(files) ==# argc()
-    for i in range(argc())
-      execute 'autocmd BufEnter' fnameescape(argv(i))
-            \ 'if empty(&filetype) || &filetype ==# "conf"'
-            \ '|doautocmd filetypedetect BufReadPost' fnameescape(files[i])
-            \ '|endif'
-    endfor
-  endif
-endfunction
-if $SUDO_COMMAND =~# '^sudoedit '
-  call s:SudoEditInit()
-endif
-
 command! -bar -nargs=? Wall
       \ if empty(<q-args>) |
       \   call s:Wall() |