* vi/vim editors stopped working after upgrade
@ 2018-03-13 15:08 d.kertz.ext
2018-03-13 15:28 ` Vince Rice
2018-03-13 18:04 ` Marco Atzeri
0 siblings, 2 replies; 3+ messages in thread
From: d.kertz.ext @ 2018-03-13 15:08 UTC (permalink / raw)
To: cygwin
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 $?
127
$ 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 $?
127
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:
$ alias
alias vi='vim'
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?
Denis Kertz
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: vi/vim editors stopped working after upgrade
2018-03-13 15:08 vi/vim editors stopped working after upgrade d.kertz.ext
@ 2018-03-13 15:28 ` Vince Rice
2018-03-13 18:04 ` Marco Atzeri
1 sibling, 0 replies; 3+ messages in thread
From: Vince Rice @ 2018-03-13 15:28 UTC (permalink / raw)
To: The Cygwin Mailing List
> On Mar 13, 2018, at 9:49 AM, d.kertz wrote:
>
> 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:
>
> …
> --
> Problem reports: http://cygwin.com/problems.html
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Start here, i.e. follow the directions on the problems page. That will give everyone needed information about your cygwin configuration.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: vi/vim editors stopped working after upgrade
2018-03-13 15:08 vi/vim editors stopped working after upgrade d.kertz.ext
2018-03-13 15:28 ` Vince Rice
@ 2018-03-13 18:04 ` Marco Atzeri
1 sibling, 0 replies; 3+ messages in thread
From: Marco Atzeri @ 2018-03-13 18:04 UTC (permalink / raw)
To: cygwin
On 13/03/2018 15:49, d.kertz.ext@nokia.com wrote:
> 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:
>
May be you need to update/reinstall the cygwin package.
https://stackoverflow.com/questions/49231333/vi-or-vim-doesnt-start-after-cygwin-update
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-03-13 17:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-13 15:08 vi/vim editors stopped working after upgrade d.kertz.ext
2018-03-13 15:28 ` Vince Rice
2018-03-13 18:04 ` Marco Atzeri
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).