From: Lee <ler762@gmail.com>
To: matthew patton <pattonme@yahoo.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>, Ken Brown <kbrown@cornell.edu>
Subject: Re: vim: errors launching "/usr/bin/vi
Date: Wed, 20 Dec 2023 14:55:33 -0500 [thread overview]
Message-ID: <CAD8GWsvenxyheYUZHRtiyS6u9NpnXcgmNRpi0foMcsmOsWujHw@mail.gmail.com> (raw)
In-Reply-To: <1367406800.2156703.1703100636276@mail.yahoo.com>
On Wed, Dec 20, 2023 at 2:30 PM matthew patton wrote:
>
> > I'd say vi/vim needs to be put under /etc/alternatives
>
> No, because that's system-wide.
Which is what I want.
> Vi vs Vim is a personal choice.
Which I've made :)
Anyone that doesn't like that decision can make their own work-around,
but me with my normal and admin logins wants 'vi' to always behave the
same way.
I kinda doubt my wife would notice.. except maybe if syntax
hilighting/coloring broke
> Also alternatives is for supporting multiple versions. Say v8.02 versus v9.1 of 'vim' on a system, one being in /usr/bin and the other in /usr/local/bin just as an example. And the sysadmin choosing (for whatever good reason) to preference the v9 software over the v8.
man alternatives
NAME
alternatives - maintain symbolic links determining default commands
It allows picking among multiple versions but it also allows picking
between different programs.
Regards,
Lee
>
> --
> 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
next prev parent reply other threads:[~2023-12-20 19:55 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
2023-12-20 20:04 ` Lee
2023-12-20 19:55 ` Lee [this message]
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=CAD8GWsvenxyheYUZHRtiyS6u9NpnXcgmNRpi0foMcsmOsWujHw@mail.gmail.com \
--to=ler762@gmail.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
--cc=pattonme@yahoo.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).