public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Beau James <b_james@pacbell.net>
To: Cygwin General + Problem Reports <cygwin@cygwin.com>
Subject: vim: errors launching "/usr/bin/vi
Date: Tue, 19 Dec 2023 18:47:17 -0800	[thread overview]
Message-ID: <da2e8ab5-f0ad-425f-a64d-fbda732fdf0c@pacbell.net> (raw)
In-Reply-To: <da2e8ab5-f0ad-425f-a64d-fbda732fdf0c.ref@pacbell.net>

[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]

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.

I encountered this because some of my longtime 'convenience' Windows 
desktop links were launching a mintty window using "vi":

>     Target: C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico
>     /usr/bin/vi /<targetfile>/

Easily fixed for me by changing "vi" to "vim". But don't know whether 
this change in behavior has any other implications?

Beau




       reply	other threads:[~2023-12-20  2:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <da2e8ab5-f0ad-425f-a64d-fbda732fdf0c.ref@pacbell.net>
2023-12-20  2:47 ` Beau James [this message]
2023-12-20  5:04   ` Marco Atzeri
2023-12-20 14:00     ` marco atzeri
2023-12-20 18:34       ` Lee
2023-12-20 18:57         ` matthew patton
2023-12-20 19:23           ` Lee
2023-12-20 19:45             ` gs-cygwin.com
2023-12-20 20:10               ` Lee
2023-12-20 19:24         ` Ken Brown
2023-12-20 19:30           ` matthew patton
2023-12-20 19:44             ` Brian Inglis
2023-12-20 19:47               ` matthew patton
2023-12-21  3:01                 ` Brian Inglis
2023-12-20 20:04               ` Lee
2023-12-20 19:55             ` Lee
2023-12-20 19:44           ` Lee
2023-12-20 19:54             ` matthew patton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=da2e8ab5-f0ad-425f-a64d-fbda732fdf0c@pacbell.net \
    --to=b_james@pacbell.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).