From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: vim: errors launching "/usr/bin/vi
Date: Wed, 20 Dec 2023 20:01:54 -0700 [thread overview]
Message-ID: <9f528cb4-959a-461b-beb7-dd6ea05fb94f@SystematicSW.ab.ca> (raw)
In-Reply-To: <134095083.2175319.1703101679543@mail.yahoo.com>
On 2023-12-20 12:47, matthew patton wrote:
>>> No, because that's system-wide.
>>> Vi vs Vim is a personal choice. Also alternatives is for supporting
>>> multiple
>> Most of us run Cygwin on a device called a /Personal Computer/ that allows
>> us to make our own choices about OS, desktop UI, services, and
>> configuration. ;^>
> yeah, yeah I know. It doesn't give license to pervert "correct behavior" though. :)
Most distros differ in their default packages and configurations for server and
desktop editions, so "correct behaviour" may also differ.
Cygwin tends to go along with Fedora desktop decisions: some features are
disabled in some packages because FESCo does not agree with some packaging
decisions or component sources.
I know some of this because I went looking to see if certain packages were
available and/or provided by default on some distro server and desktop editions,
and found that most of those decisions and that information is not really
documented in any obvious place, just implemented, so you would have to install
and run the editions to find out!
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-12-21 3:01 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
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 [this message]
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=9f528cb4-959a-461b-beb7-dd6ea05fb94f@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).