From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12olkn2080f.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe5b::80f]) by sourceware.org (Postfix) with ESMTPS id 5F6A43858D39 for ; Sun, 14 Nov 2021 18:56:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5F6A43858D39 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WI/2/jKOUBk8d3rS79TSo9AoZyfo60RFA8l9nje+zRm4+TFibaoDs+of/YfNk7wPdl7rXDdcRhmazOuXFGnnGrPZ7DTB40FHZhkAlVaCNU5y9xPdzaMHiL6/cSLxjQiFqhYUYHtBv8xq9QH+cMD18xOvAkGjk/XUkoo0+TiBgrrcvPp9dkeTGebM+AVnxQZO+EyHW8m6YDYWT2/ipPRqvh9fnDRyvSpbTA1k1LCyNTqqP1V3RIRcXb51Un5rlBKhElvGhiheIHP9yLGzhLqg6EMzJzE/fufrH+u+U82k5MKFHc3L15QHbxhP/k9fI6pKfTG3otkVmq8gI+dh8ESbkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=zbEnGJP01oAgGgwHdZjlMc+eCH8ivTTxl59YgvVQp84=; b=SXUTy46deohYY0NBnRpZqxjVSeYSEV2LDVvdievZ6TpXEfozditGut3MgoYfDwZza8kwKkXCewcsaI+x7FhvkoChBL6dx/4SHxLuuG/+jXw6V5p6JWvFP6b9v0jznQmzWVPeTm6J81p3imP/aPb82no2KA8Yc4zpwUIJ3HMgGsJrPJ0XyBjDcPm9YgLjXU/a7jENCaL44yYzNqw6XI5XxQA5QMVob5yeeXlj+cTgBCE+QetHRK60Hvs3oy1MNCus0ShkUBdJ5b9wJq7OEhe57D+LL/iiFaar+MDBYXSrgXOQMwOnyQmyyYAxwZgJP+ylJRqJjAzBVCIV5q8jgj6AXg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none Received: from SN6PR04MB4799.namprd04.prod.outlook.com (2603:10b6:805:b0::26) by SA0PR04MB7354.namprd04.prod.outlook.com (2603:10b6:806:e9::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4690.17; Sun, 14 Nov 2021 18:56:29 +0000 Received: from SN6PR04MB4799.namprd04.prod.outlook.com ([fe80::95be:545b:5994:dba4]) by SN6PR04MB4799.namprd04.prod.outlook.com ([fe80::95be:545b:5994:dba4%6]) with mapi id 15.20.4669.021; Sun, 14 Nov 2021 18:56:29 +0000 From: Steve Ward To: "cygwin@cygwin.com" Subject: Editing with vim clears Windows 10 file system archive bit. Thread-Topic: Editing with vim clears Windows 10 file system archive bit. Thread-Index: AQHX2YjfqUWVEwVDT0KOl/dB9rU2+w== Date: Sun, 14 Nov 2021 18:56:29 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-tmn: [nCIFHkGsONHqFjs9KhWmZonmE01zLO/2] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: a88f71a7-049b-40bd-ea99-08d9a7a077e5 x-ms-traffictypediagnostic: SA0PR04MB7354: x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: QC9Ebcg0W/BkwQjBklaRLs3dFWOw/J4Du0qNPdnOXGiJ5QATl8654b+xZp8h2M2jqVGJPWe08AtHZVSxQTDSlSQB4Bd05z+7WEj6h7QBKZGxr8ww5ymuKeBZOms8GTZm4h1H6HpVhvdqxraJGWoSzE3YbbeRHrxTM//U8JJbSSu075JEFR650SSMhMjD8TmLRc7h2YT9HN25r47j8TV2uZ3OPXteTq83ejhM8KcybplA/VQDTUwsAzzgyQhxOTjoHKtFzfPEzrIJFjIN+oChlXzyfcBif8/ecm9Wl2PPeUf9uEqQxQjlZebBOHql+62jgZ2SkUWBwJuUAy6RKDn0HCxQLeBJwb9jHfzLTWQifCssmxNy1xOzCqKxWIi2G2va/4kelZOJcUOnPwaCBjSB2ebaXHdrCc9DrqMs5qBh1z1LNPjGwPPtIvfWk/2GwbgCIT8At3xAg7vMsNTNO9dXjJ1hm6636otCDlb/2GuZvts375v3FXGHkrjv08SsEKi31kYY04qewGnRqLTX3i0ijGylSox1rGx1/fG+dGVpoGRSP/6zgZ8vqH0c98L43htVe8wdc6I+juBqcu2h14xsoQ== x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: r0TkdZ6xk4qnPWS2/TMy5uUVcD7VchmpPNbipySHEpk3ZRSDO84PH74QHLinpnN5Jo1C2t73gnZjClefon3MtoIyeq/I206bAF5LbQtF9ivQUQM/nN98Cb2rQOcAl7xB9X88WS81eV+e//ta1IpYsUTTu47WtE5Zbc9TigxQ4qL57vwo5DhddgpULwOp9awnnnopwtpWoxa1NdYI3oFgYeP2iOonL04EOw1P+CjxaM+Iu9Romn6Hw+ETwZtqymPausMSnjFoVdhGj4kB/UI7F11WqJuPPGgW+pilZ/kfiJBDCFvuqwdFc2diboadhfGOz6iH49ONNviTJXR+pyDwrr5w+Q3OxHsytkfn7/8W+B0ew3XGuTyzUsmpdwjDDKX+C04AlBgogmlxf2yrzL/VtQI3uGeh6yKjHWOeDrk4GPA6T0pG0mq7CMV+MmdlmTZNOgusG1ulCyqZa7ZhE3oeiysdhYkYr5aFtcjLHWdr1dA0UjHeg8oiOoZuWk2D0MXjwOHnKJQcuU4ZVvleFqgZLrxNeNoejTWBHVhTqQAfJx/J1RKHM9U6Bzkp9kfG9N/nTOCDYZBETwAMWJFdl1tv18/1A/uLRn35E9kQCswjOvdQ7XGPAJL+VNLTo7TtvbvpMjyWBAvrMwWIOQYBzmJxJG3n034vqzcyRPLGa7u1TvB+CDX1C14pgZWPLaCjXVj2nRnRwSHk/+DSjTtsIyCqWA== MIME-Version: 1.0 X-OriginatorOrg: sct-15-20-3174-20-msonline-outlook-529c7.templateTenant X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: SN6PR04MB4799.namprd04.prod.outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: a88f71a7-049b-40bd-ea99-08d9a7a077e5 X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Nov 2021 18:56:29.6489 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA0PR04MB7354 X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, HTML_MESSAGE, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2021 18:56:37 -0000 Description of problem: While using vim 8.2 on cygwin 3.3 (x86_64) on Windows 10, when editing an existing file with vim and saving it, the Window=92s file system archive bit is always left cleared (not modified state). This happens, whether the archive bit was set (is modified) or clear (not modified) initially. Window=92s backup tools rely on this archive bit for making incremental backups. The following scenarios DO work: 1. Using vim to create a new file, leaves the new file=92s archive bit set (is modified). 2. =93cp=94 and redirect with append (=93>>=94), leave the target file=92s archive bit set (is modified). 3. =93emacs=94 (emacs-w32) (ver. 27.2) worked for both editing and creating= ! 4. Editing with vim sets the =93last modified date=94 correctly for Linux and Windows. Tools used to confirm the problem: The cygwin tool, =93cygcheck =96c=94 listed =93OK=94 as the status of every= package. The archive bit settings were confirmed with Window=92s =93File Explorer=94= and cygwin=92s =93attrib=94. The cygwin tool, =93chattr,=94 could be used as a crude workaround, but I rather have vim do it. My search for solutions: I have perused 8 years of =93The Cygwin Archives=94 for this issue, but could find nothing relevant. Google Web searches, and stackoverflow.com, vim.org and vi.stackexchange.com searches turned up nothing relevant. On my local machine, a search of /usr/share/vim/vim82/doc/*.txt turned up nothing relevant. My update history: 10/2013 Cygwin-1.7.25 Windows 8 vim-7.3.1314 No problem with archive bit. 09/2021 Cygwin-3.2.0 Windows 10 vim-8.2.0486 Problem with archive bit. 11/2021 Cygwin-3.3.2 Windows 10 vim-8.2.0486 Problem with archive bit. Can anyone shed some light on this issue? Thanks, Steve Sent from Mail for Window= s