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
c
On Wed, Dec 20, 2023 at 2:45 PM gs-cygwin wrote:
>
> 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.
Wow! I would have never guessed 'wrapper script'
On Wed, Dec 20, 2023 at 2:44 PM Brian Inglis wrote:
>
> On 2023-12-20 12:30, matthew patton via Cygwin wrote:
> >> I'd say vi/vim needs to be put under /etc/alternatives
>
> > No, because that's system-wide.
> > Vi vs Vim is a personal choice. Also alternatives is for supporting multiple
> > versio
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-aroun
> 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=
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.
>> 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
On Wed, Dec 20, 2023 at 2:24 PM Ken Brown via Cygwin wrote:
>
> 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:
> T
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:
# -
On 2023-12-20 12:30, matthew patton via Cygwin wrote:
I'd say vi/vim needs to be put under /etc/alternatives
No, because that's system-wide.
Vi vs Vim is a personal choice. Also alternatives is for supporting multiple
versions. Say v8.02 versus v9.1 of 'vim' on a system, one being in /usr/bin
> I'd say vi/vim needs to be put under /etc/alternatives
No, because that's system-wide.
Vi vs Vim is a personal choice. 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.
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".
On Wed, Dec 20, 2023 at 1:57 PM matthew patton wrote:
>
> > Would you please let me know how to make an /etc/alternatives for vi/vim?
>
> did you install the alternatives package?
I installed cygwin back in 2017; I don't remember what all I've
installed but it seems to be there:
$ ls -l /usr/sbin/
> Would you please let me know how to make an /etc/alternatives for vi/vim?
did you install the alternatives package? I just use aliases (actually I set
EDITOR=xxx) after I enumerate the editors I consider worthy of inclusion and
resident. What DOES need nuking is the forced alias in /etc/profile
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
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
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".
My Cygwin installation now show vim version 9.0.2115.
Launching VIM from the shell running in a mintty window using the full
pathname "/usr/bin/vim" work
This problem appeared with my most recent Cygwin update that included an
update to "vim".
My Cygwin installation now show vim version 9.0.2115.
Launching VIM from the shell running in a mintty window using the full
pathname "/usr/bin/vim" works fine.
But launching "/usr/bin/vi" (which has wo
17 matches
Mail list logo
