From: gs-cygwin.com@gluelogic.com
To: Lee <ler762@gmail.com>
Cc: matthew patton <pattonme@yahoo.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: vim: errors launching "/usr/bin/vi
Date: Wed, 20 Dec 2023 14:45:08 -0500 [thread overview]
Message-ID: <ZYNERJVf0yNjSIQ6@xps13> (raw)
In-Reply-To: <CAD8GWsu7hFAgAZQBzDf5_YO_GfWCxn=6dNMtg092Bq9XUFQDyw@mail.gmail.com>
On Wed, Dec 20, 2023 at 02:23:49PM -0500, Lee via Cygwin wrote:
> If anyone has access to a redhat linux system, do they 'alias vi=vim'
> or put vi under /etc/alternatives?
FYI: neither.
$ cat /etc/fedora-release
Fedora release 39 (Thirty Nine)
$ cat /usr/bin/vi
#!/usr/bin/sh
# run vim if:
# - 'vi' command is used and 'vim' binary is available
# - 'vim' command is used
# NOTE: Set up a local alias if you want vim -> vi functionality. We will not
# do it globally, because it messes up with available startup options (see
# ':help starting', 'vi' is not capable of '-d'). The introducing an environment
# variable, which an user must set to get the feature, will do the same trick
# as setting an alias (needs user input, does not work with sudo), so it is left
# on user whether he decides to use an alias:
#
# alias vim=vi
#
# in bashrc file.
if test -f /usr/bin/vim
then
exec /usr/bin/vim "$@"
fi
# run vi otherwise
exec /usr/libexec/vi "$@"
next prev parent reply other threads:[~2023-12-20 19:45 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 [this message]
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=ZYNERJVf0yNjSIQ6@xps13 \
--to=gs-cygwin.com@gluelogic.com \
--cc=cygwin@cygwin.com \
--cc=ler762@gmail.com \
--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).