DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 876D03858439
Message-ID: <7d0e764a-3f03-42c8-a6f3-63355e218f1e@gmail.com>
Date: Wed, 20 Dec 2023 06:04:21 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: vim: errors launching "/usr/bin/vi
Content-Language: en-US
To: cygwin@cygwin.com
References: <da2e8ab5-f0ad-425f-a64d-fbda732fdf0c.ref@pacbell.net>
 <da2e8ab5-f0ad-425f-a64d-fbda732fdf0c@pacbell.net>
In-Reply-To: <da2e8ab5-f0ad-425f-a64d-fbda732fdf0c@pacbell.net>
From: Marco Atzeri via Cygwin <cygwin@cygwin.com>
Reply-To: Marco Atzeri <marco.atzeri@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

On 20/12/2023 03:47, Beau James via Cygwin wrote:
> This problem appeared with my most recent Cygwin update that included an 
> update to "vim".
> 
> My Cygwin installation now show vim version 9.0.2115.
> 
> Launching VIM from the shell running in a mintty window using the full 
> pathname "/usr/bin/vim" works fine.
> 
> But launching "/usr/bin/vi" (which has worked fine for many years, until 
> the most recent update), results in a long string of startup E319 errors:
> 
>>     $ /usr/bin/vi
>>     Error detected while processing /usr/share/vim/vim90/filetype.vim:
>>     line   11:
>>     E319: Sorry, the command is not available in this version: let
>>     did_load_filetypes = 1
>>     line   14:
>>     E319: Sorry, the command is not available in this version: let
>>     s:cpo_save = &cpo
>>     line   48:
>>     E319: Sorry, the command is not available in this version: func
>>     s:StarSetf(ft)
>>     line   52:
>>     E319: Sorry, the command is not available in this version: endfunc
>     etc. etc.
> 
> Note that the startup errors appear only when using the full pathname 
> "/usr/bin/vi". Using the command name alone ("vi") relying on the search 
> path does not trigger the startup errors; using either the full pathname 
> "/usr/bin/vim" or the command name alone "vim" relying on the search 
> path does not trigger the startup errors.
> 

vi is usually an alias to vim

$ alias | grep vi

  alias vi='vim'

so you are in reality calling vim

$ which vim
/usr/bin/vim


I am investigating the /usr/bin/vi issue


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple