sops fails to edit file when $EDITOR contains arguments about sops HOT 5 CLOSED

(assume-aws-role prod)$ EDITOR='vim' sops common.yaml
INFO: assuming AWS role 'arn:aws:sts::361527076523:assumed-role/hiera-sops-prod/sops@jbuckley-23775'
INFO: temp file created at /var/folders/q2/vhg0j08n3fz3zsvph1rsw5080000gn/T/tmpRDS4a1.yaml
PANIC: common.yaml has not been modified, exit without writing
(assume-aws-role prod)$ EDITOR='vim -C' sops common.yaml
INFO: assuming AWS role 'arn:aws:sts::361527076523:assumed-role/hiera-sops-prod/sops@jbuckley-23775'
INFO: temp file created at /var/folders/q2/vhg0j08n3fz3zsvph1rsw5080000gn/T/tmp_tnTJ0.yaml
OSError: [Errno 2] No such file or directory
(assume-aws-role prod)$ EDITOR='vim ' sops common.yaml
INFO: assuming AWS role 'arn:aws:sts::361527076523:assumed-role/hiera-sops-prod/sops@jbuckley-23775'
INFO: temp file created at /var/folders/q2/vhg0j08n3fz3zsvph1rsw5080000gn/T/tmpdQLbuN.yaml
OSError: [Errno 2] No such file or directory

--resume (no short variant) Used in combination with -w or --wait, this switch
will cause the application which was frontmost when the bbedit tool was invoked
to be made frontmost again once you close the file(s) specified on the command
line.

  This is convenient if you are using the Terminal (or any third-party
  equivalent) to invoke a command which uses BBEdit as its editor (p4, cvs), and
  want to return back to the Terminal when the editing session is over.

    bbedit --wait --resume  ~/foo.txt

-w, --wait Wait until the file is closed in BBEdit. Normally, the bbedit tool
exits immediately after the file arguments are opened in BBEdit. This option
applies to both local files and files opened from FTP or SFTP servers.

  The -w option allows the bbedit tool to be used as an external editor for Unix
  tools that use the EDITOR global environment variable. To make this work using
  tcsh, add the following line to your .cshrc (or .tcshrc) file:

    setenv EDITOR "bbedit -w"

  Some tools (notably crontab), will not work correctly if your EDITOR variable
  consists of multiple terms. You can work around this by creating a simple
  shell script that calls bbedit -w, then using the shell script as your EDITOR.
  For example:

    #!/bin/sh
    bbedit -w "$@"