Hi Marco, On Wed, 29 Jan 2025 16:23:03 +0100 Marco Atzeri wrote: > On 29/01/2025 16:02, Takashi Yano via Cygwin wrote: > > Hi Achim, > > > > On Wed, 29 Jan 2025 13:30:16 +0100 > > ASSI wrote: > >> Marco Atzeri via Cygwin writes: > >>> It works fine from my side and there were no patch on filetypes.vim so > >>> it is vanilla based. > >> > >> Hmmm… it actually works when I explicitly start vim, but I get the error > >> when I start vi. I have another system where it's OK, so let me do a > >> re-install of all related packages and see what happens. Maybe there > >> was some hiccup during the last update that I didn't catch. > > > > I also encountered the same issue, however, the issue is not > > reproducible now. Probably, removing ~/.viminfo affects somehow? > > However, I think /usr/bin/vi does not read .viminfo, does it? > > > Hi Takashi, > > It is not an issue of .viminfo. I removed it and > /usr/bin/vi reports anyway the issue as Achim wrote
Indeed. I reinstall vim 9.1.1054, then the issue came back... "filetype plugin on" in /etc/virc might be the culprit. -- Takashi Yano <takashi.y...@nifty.ne.jp> -- 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
