On Wed, Dec 20, 2023 at 2:24 PM Ken Brown via Cygwin <cygwin@cygwin.com> 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: > >>>> 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 reality calling vim > >>> > >>> $ which vim > >>> /usr/bin/vim > >>> > >>> > >>> I am investigating the /usr/bin/vi issue > >>> > >> > >> -2 version should have solved the issue > > > > I don't get any error or warning messages now but 'vi' still doesn't > > always get me the same thing: > > > > $ vi --version | head -5 > > VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Dec 20 2023 06:57:02) > > Included patches: 1-2155 > > Modified by <cygwin@cygwin.com> > > Compiled by <cygwin@cygwin.com> > > Huge version without GUI. Features included (+) or not (-): > > > > $ /bin/sh > > > > $ vi --version | head -5 > > VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Dec 20 2023 06:53:22) > > Included patches: 1-2155 > > Modified by <cygwin@cygwin.com> > > Compiled by <cygwin@cygwin.com> > > Tiny version without GUI. Features included (+) or not (-): > > Your second shell is not a login shell. Could that be the problem?
You need to define "problem" first :) I want "vi" to always call "vim" .. hrmm.. unless I've explicitly done something to explicitly over-ride that. So anytime I type in 'vi' and don't get the VIM Huge version without GUI I'd say that's a problem. I've got "export EDITOR=vi" in my .bash_profile, so anytime $EDITOR is called I want the huge version of vim. If that doesn't happen I'd say that is a problem. If I'm in a bash sheel & do /bin/sh I expect typing in 'vi' will get me the same results as when I was in bash Same deal with dash -- I still want my expected version of vim to run So ... a very long way of saying No, I don't think the second shell not being a login shell is 'the problem.' My experience is that Debian always does the right thing wrt vi/vim. Cygwin does not. It'd be interesting to know if redhat linux uses alternatives or an alias to decide which vi/vim gets called. 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
