The special handling of vi is just fine. The whole problem is that not only the vi behaviour changed, but also the vim behaviour. Which is why I suggested the solutions I suggested.
2013/12/9 Frank Fesevur <f...@users.sourceforge.net>: > 2013/12/9 Björn Kautler: >> Again, what I talk about is NOT an issue of vi vs. vim. >> What I talk about is a breaking change in vim that was introduced >> while doing a change for vi. >> But it is NOT an issue of vi vs. vim. > > That patch was introduced when people started to complain that they > got errors about commands not recognized in their vimrc. The root > cause of this was obviously the whole vi != vim thing. > > I always use ~/.vimrc so I never ran into your problem. > > Regards, > Frank > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
