This is the mail archive of the
mailing list for the Cygwin project.
vi/vim editors stopped working after upgrade
- From: <d dot kertz dot ext at nokia dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 13 Mar 2018 09:49:10 -0500
- Subject: vi/vim editors stopped working after upgrade
- Authentication-results: sourceware.org; auth=none
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
After applying pending updates and adding the make package, the vi/vim editors stopped working. Running either vi or vim with or without the hard-coded path just returns exit code 127:
$ whereis vi
vi: /usr/bin/vi.exe /usr/share/man/man1/vi.1.gz
$ ls -l /usr/bin/vi.exe
-rwxr-xr-x 1 (owner/group names stripped) 1014803 Mar 4 23:30 /usr/bin/vi.exe
$ /usr/bin/vi cygcheck.out
$ echo $?
$ whereis vim
vim: /usr/bin/vim.exe /usr/share/vim /usr/share/man/man1/vim.1.gz
$ ls -l /usr/bin/vim.exe
-rwxr-xr-x 1 (owner/group names stripped) 2645011 Mar 4 23:30 /usr/bin/vim.exe
$ /usr/bin/vim cygcheck.out
$ echo $?
Searching suggests that exit code 127 means the command is not found but using a hard-coded path should rule that out.
There is an alias:
but that shouldn't come into play using a hard-coded path and setting the vi alias to nothing doesn't change anything.
Changing to /usr/bin/sh rather than bash doesn't change anything.
The vi/vim editors were re-installed and that doesn't change anything.
Note that command line editing works fine.
Anyone know what might be going on?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple