From: matthew patton <pattonme@yahoo.com>
To: Ken Brown <kbrown@cornell.edu>, Lee <ler762@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: vim: errors launching "/usr/bin/vi
Date: Wed, 20 Dec 2023 19:54:14 +0000 (UTC) [thread overview]
Message-ID: <1104443108.2167819.1703102054256@mail.yahoo.com> (raw)
In-Reply-To: <CAD8GWsveCnpmroy3fjkTd_qigOgcBgfEr-=0_7cZAqZ1QBJ9nQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
> I've got "export EDITOR=vi" in my .bash_profile, so anytime $EDITOR is
> called I want the huge version of vim.
Then set EDITOR=<path_to_vim>
If you want to cheat and only use 'vi' then you need to walk the dependency chain and/or search_for_binary mechanism employed by the SHELL to find the correct target. You can of course set this as 'system-wide global' or down in your login shell, or in sub-shell scope.
It is NOT the application packager's job to do your homework for you, or to hijack the process because some percentage of people prefer it a certain way.
Also, you seem to be not aware that /bin/sh RARELY actually invokes BASH. On some Linux distros it does, but you should NOT rely on that being true anywhere else.
prev parent reply other threads:[~2023-12-20 19:54 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
2023-12-20 19:44 ` Lee
2023-12-20 19:54 ` matthew patton [this message]
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=1104443108.2167819.1703102054256@mail.yahoo.com \
--to=pattonme@yahoo.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
--cc=ler762@gmail.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).