Page MenuHomePhabricator

If "vi" or "vim" exit with an error code, test for error-on-interactive-mistake behavior
ClosedPublic

Authored by epriestley on May 24 2019, 8:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jul 1, 7:16 PM
Unknown Object (File)
Mon, Jun 30, 5:02 PM
Unknown Object (File)
Sun, Jun 29, 6:10 AM
Unknown Object (File)
Wed, Jun 25, 10:03 AM
Unknown Object (File)
Wed, Jun 25, 1:37 AM
Unknown Object (File)
Thu, Jun 5, 4:25 PM
Unknown Object (File)
May 25 2025, 2:26 PM
Unknown Object (File)
May 20 2025, 6:18 AM
Subscribers
None
Tokens
"Baby Tequila" token, awarded by avivey.

Details

Summary

See T13297. Some versions of "vi" and "vim" exit with an error code if the user makes a command typo while performing an interactive edit. This can lead to discarding stuff they typed.

If we receive an error code:

  • test if the binary is "vi" or "vim";
  • if it is, test if "<binary> +q +Q" exits nonzero;
  • if it does, ignore the error code.

This appears to be a conclusive test for "error indicates interactive command mistake".

Test Plan
  • On my system, ran EDITOR=... arc diff --trace with vi and vim.
  • Made an intentional command typo, e.g. :Q<enter> in command mode.
  • Saved with :wq.
  • Before, vim: worked fine.
  • After, vim: worked fine.
  • Before, vi: failed after vi exited with an error.
  • After, vi: detected the error in vi, detected questionable vi binary behavior, workflow recovered and succeeded.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable