From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: vim: errors launching "/usr/bin/vi
Date: Wed, 20 Dec 2023 14:24:32 -0500 [thread overview]
Message-ID: <e238b979-0722-48e5-bd8f-32608cd8b734@cornell.edu> (raw)
In-Reply-To: <CAD8GWsv6DiwdVA_ODiK5GYkQoDqfWEyxCOoJvCmmboNJwN_5hA@mail.gmail.com>
On 12/20/2023 1:34 PM, Lee via Cygwin wrote:
> On Wed, Dec 20, 2023 at 9:01 AM marco atzeri wrote:
>>
>> On Wed, Dec 20, 2023 at 6:04 AM Marco Atzeri wrote:
>>>
>>> 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".
>>>
>>> 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
>>>
>>
>> -2 version should have solved the issue
>
> I don't get any error or warning messages now but 'vi' still doesn't
> always get me the same thing:
>
> $ vi --version | head -5
> VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Dec 20 2023 06:57:02)
> Included patches: 1-2155
> Modified by <cygwin@cygwin.com>
> Compiled by <cygwin@cygwin.com>
> Huge version without GUI. Features included (+) or not (-):
>
> $ /bin/sh
>
> $ vi --version | head -5
> VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Dec 20 2023 06:53:22)
> Included patches: 1-2155
> Modified by <cygwin@cygwin.com>
> Compiled by <cygwin@cygwin.com>
> Tiny version without GUI. Features included (+) or not (-):
Your second shell is not a login shell. Could that be the problem?
Ken
next prev parent reply other threads:[~2023-12-20 19:24 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
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 [this message]
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=e238b979-0722-48e5-bd8f-32608cd8b734@cornell.edu \
--to=kbrown@cornell.edu \
--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).