DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 50TF3IYK2906071 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 50TF3IYK2906071 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=yzC0ZhaH X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 99BEA3857BB9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1738162996; bh=BUwSW2zjK28DNgLHKm/cY0saGF1LXw9gfoi0tR/Jhxc=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=yzC0ZhaHPrU/D88jCSE6BtPm0jYVgyA4qeItR0MG/KXKK9MduzfXorJvnsRF99S4j IWPeyu8cHo+1MIAaF5XUWBZUN7BLQFST1Ge1gRrSnc5XD4pIKkMOJmVEnhNwsvZfC2 L5CN7l0iAfRpuEbZil9go6ouikBwjxtYsDqCnz4E= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8A3103858D34 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8A3103858D34 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1738162959; cv=none; b=IuZYouUdL5SrWBsBzJ3ajlCrv7AmuHLbcG0dKN2B3TzaKz2hXKPIk/mTREKGY4DJzR3MSjfuWe9VNl+4Mmp40UgIsXNqqkGkVZ2P7Ap3db2fnNKCDX7+4TYzmLDcYjSxglCw/IikXtkQyZAgCHMQDvLcXgAwEmALp1al8TpnpPc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1738162959; c=relaxed/simple; bh=GRf7U+kNiwZgfaS3MZ/GnaWy8eYM+Y2Ba+bywJZAQ2s=; h=Date:From:To:Subject:Message-Id:Mime-Version:DKIM-Signature; b=KU4oliIjPSKtn5EBXxZmn2ND3f5SNbkQ9v0+anBxVrMnw0XCq/y2APntB2Latx7u1xJKme3HAjKXsTMnMESSZrTLhpjNkHN7kLMD8mFU0op1xpA7YowD58m0u4Y8nCAqQRxM7dfSa3SKYIjOEJcrpOLA81QrymNuuylrrsGMjDw= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8A3103858D34 Date: Thu, 30 Jan 2025 00:02:35 +0900 To: cygwin AT cygwin DOT com Subject: Re: Updated: vim-9.1.1054-1 Message-Id: <20250130000235.f0ee5a6f3c3b30603389e292@nifty.ne.jp> In-Reply-To: <87y0ytztt3.fsf@> References: <679a02d4 DOT 050a0220 DOT 31ceeb DOT 11b6SMTPIN_ADDED_BROKEN AT mx DOT google DOT com> <1691def4-2798-4c96-b6dc-03d40a7f4f3b AT gmail DOT com> <57eaf1c8-9645-43a1-ad2d-c43fab12db4b AT gmail DOT com> <87y0ytztt3.fsf@> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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? -- Takashi Yano -- 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